Trillium R1 2026 Changes and required actions
Functional Area | Change or Additions | Considerations | Action timing, | Comments | Contact person, |
|---|---|---|---|---|---|
mod-search | instance, instance_classification index mapping changes |
| After upgrade. Reindex is needed. Upload reindex of instances, classifications is sufficient. Use
|
| @Viacheslav Kolesnyk https://folio-org.atlassian.net/browse/MSEARCH-1045 https://folio-org.atlassian.net/browse/MSEARCH-1067 @Khalilah Gambrell @Christine Schultz |
mod-inventory-storage | The breaking change was introduced for endpoints that do create/update item operations. Updated API versions
|
| No specific action needed, migration is performing during module upgrade |
| @Pavlo Smahin |
mod-reporting | When reports are invoked from a GitHub or GitLab repository, they are now checked against a whitelist included in the top-level configuration file under the key | Reports whose URLs do not match one of the whitelist entries will be refused for security reasons. | Each installation’s whitelist should be configured appropriately by updating the | If the default configuration is blindly used, previously working reports will stop working. | |
mod-circulation | New boolean environment variable ENABLE_FOR_USE_AT_LOCATION; defaults to | To allow a single tenants items to be only circulated as items only For use at location (Reading room loans). The functionality require the loan policy, the service point setting, and the circulationrules to be set up to support For use at location functionality. If the library do For use at location loans, then the environment variable must be present and set to | The variable can be set at any time. |
| @Charlotte Whitt @Niels Erik Nielsen |
mod-source-record-manager | The default MARC-to-Instance mapping rules have been updated for the 338 field (Instance Format). |
| Migration is performed during the module upgrade process. Ensure that it is successful; otherwise, perform a manual upgrade. Refer to the details for further instructions. |
| @Kateryna Senchenko |
mod-entities-links | scope for authority expiration settings changed from | mod-settings will have 2 entries for | In case this setting was modified by the users - they’ll need to modify a new one. Old setting entry may be removed since it will no longer be used. | Scope was changed to support eureka permission name pattern.
Note: We know for sure that LOC modified this value to never delete authority records. | @Viacheslav Kolesnyk @Christine Schultz |
mod-specifications | Change API default to false for the following endpoints
| This is a global change. |
| This is a global change and if a library wants catalogers to be warned of undefined fields/indicators/subfields then they will need to change these endpoints to true. | https://folio-org.atlassian.net/browse/MRSPECS-102 @Khalilah Gambrell |
mod-specifications | MARC Specifications Update: Add new subfields and update existing subfields (Bibliographic & Authority) based on latest MARC Standards | Execution is optional and applicable only for libraries using MARC validation in Ramsons/Sunflower. | After upgrade. | Execution of this script is optional and it should be run only if the library has enabled MARC bibliographic or MARC authority record validation in Ramsons/Sunflower. | @Svitlana Kovalova |
ui-tags/Settings - Tags | The "Enables tags" flag in Settings -> Tags -> General has changed its endpoint. |
| After upgrade. If this flag was turned off in your environment before the upgrade, you need to turn it off manually again. | The endpoint change means previous settings will not persist during upgrade. | @Dmytro Melnyshyn @Stephanie Buck |
mod-users | The endpoint for preventing specific users from being edited or deleted (suppressEdit) has moved from the old | Administrators need to migrate existing suppressEdit configurations to the new endpoint. | After upgrade. Migrate suppressEdit configurations using the new | Migration is required if suppressEdit was configured. This setting prevents designated users from accidental editing or deletion. | @Dmytro Melnyshyn @Stephanie Buck https://folio-org.atlassian.net/browse/UIU-3404 |
mod-users | The endpoint for configuring a user profile-picture functionality has been moved from | The existing configuration which is accessed and managed with |
| Instructions for manually creating the profile-picture configuration through | @Mukhiddin Yusupov @Stephanie Buck |
mod-settings | New API to set UI URL | Call PUT /base-url when adding a new tenant or changing the UI URL of a tenant | After upgrade. | Formerly known as FOLIO_HOST | @Julian Ladisch https://folio-org.atlassian.net/browse/MODSET-39 |
mod-entities-links | Authority propagated data cleanup in consortium Member tenants | Cleanup of duplicate instance–authority links and authority shadow copies in member tenants. | After upgrade. | Only in consortium environment for a member tenant | https://folio-org.atlassian.net/browse/MODELINKS-388 |
mod-gobi | Standard database connection environment variables must be added to the module configuration. | The migration of existing mappings to the new | Before upgrade when specifying env variables for mod-gobi | A new | https://folio-org.atlassian.net/browse/MODGOBI-217 @Serhii_Nosko |
mod-inventory-storage | Item records now have property | To populate the field for all item records there is a need to execute for each tenant background async migration | After upgrade. | Performance test result could be reviewed: https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1864302598 | @Pavlo Smahin |
mod-agreements | New boolean environment variable | Using acquisition units (from mod-orders - see https://docs.folio.org/docs/settings/settings_acquisition_units/settings_acquisition_units/) to control access to specific Agreements/Agreement lines has an impact on performance as it means extra lookups each time a user interacts with the agreement/agreement line to look up their access based on Acquisition Units. If a tenant does not wish to use Acqusition Units for Agreements, this variable can be set to | After upgrade |
| @Owen Stephens |
mod-licenses | New boolean environment variable | Using acquisition units (from mod-orders - see https://docs.folio.org/docs/settings/settings_acquisition_units/settings_acquisition_units/) to control access to specific Licenses/Amendments has an impact on performance as it means extra lookups each time a user interacts with the license/amendment to look up their access based on Acquisition Units. If a tenant does not wish to use Acqusition Units for Licenses, this variable can be set to | After upgrade |
| @Owen Stephens |
mod-search |
| Action is not required for all deployments. Apply in case of encountering error like “Cannot get data from search/consortium/batch/holdings“ during Bulk-Edit file upload | Apply at runtime (after upgrade) if issues appear. Set | For more details on issue which could be fixed by this change see comments in related JIRAs | @Viacheslav Kolesnyk |