Trillium R2 2025 Changes and required actions

mod-search

instance, instance_classification index mapping changes

After upgrade.

Reindex is needed. Upload reindex of instances, classifications is sufficient.

Use /search/index/instance-records/reindex/upload with body:

{ "entityTypes": [ "instance", "classification" ] }

@Viacheslav Kolesnyk
@Pavlo Smahin

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.
The itemLevelCallNumberTypeId property can now be only a UUID that exists in the call_number_type table.

Updated API versions

• item-storage 11.0

• item-storage-batch-sync 2.0

• item-storage-batch-sync-unsafe 2.0

No specific action needed, migration is performing during module upgrade

@Pavlo Smahin
https://folio-org.atlassian.net/browse/MODINVSTOR-987

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 reportUrlWhitelist.

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 config.json file (see the README file). Note that, if using the stock Docker container image, you will need to mount your copy of the file over the default.

If the default configuration is blindly used, previously working reports will stop working.

https://folio-org.atlassian.net/browse/MODREP-4

mod-circulation

New boolean environment variable ENABLE_FOR_USE_AT_LOCATION; defaults to false

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 true

The variable can be set at any time.

@Charlotte Whitt @Niels Erik Nielsen

https://folio-org.atlassian.net/browse/CIRC-2457

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

https://folio-org.atlassian.net/browse/MODDICORE-456

mod-entities-links

scope for authority expiration settings changed from authority-storage to authority-storage.manage

mod-settings will have 2 entries for authority-archives-expiration key, 1 with old scope and 1 with new scope. Only entry with new scope will be used by mod-entities-links.

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

• PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Field"}

• PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Subfield"}

• PATCH /specification-storage/specifications/{MARC bib or authority specificationId}/rules/{global rule id for rule name "Undefined Indicator Code"}

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