Trillium R1 2026 Notes on functionality

MOD-CONFIGURATION DECOMISSION

App	Notes	Jira	Product Owner

App	Notes	Jira	Product Owner
Orders	Validation of ISBNs no longer occurs when adding an ISBN as a product identifier to an order line. Additionally, ISBN-10 is no longer converted to ISBN-13. (Please note that this has also been backported to Ramsons as of CSP #4 and Sunflower as of CSP #1). The "User Limit" (`poLine.eresource.userLimit`) is now an alphanumeric string value rather than an integer. Orders alerts and reporting codes (`reportingCodes` and `alerts`) have been removed from the `poLine` to utilize a single order line schema. (Note: All migrations for these updates will be applied automatically, and we do not anticipate any effort will be required from other teams.)	https://folio-org.atlassian.net/browse/UIOR-1335 https://folio-org.atlassian.net/browse/UIOR-1023 https://folio-org.atlassian.net/browse/MODORDERS-1269	@Joseph Reimers /@Serhii_Nosko
eUsage	Counter 5.1 Support Manual upload Counter 5.1 reports for usage data providers in the file formats TSV, CSV and XLSX. Support for Counter 5.1 is now complete. All other features have been available since the FOLIO release Sunflower. Manual upload of Counter reports Improvement of the notification of exceptions when manually uploading COUNTER files. Form for manually uploading Counter reports updated in terms of content and appearance. Manually changed Counter reports New icon for Counter reports in the statistics table that have been changed manually. The icon is a pencil. Exception handling CoP 3030 (No Usage Available for Requested Dates) / 0-Reports. In the UI, Counter reports with error code 3030 have a new icon. The icon is a circle. Report info: Counter exception codes 2011, 3032, 3063 added to the translations. Report info: Improvement of the report info when HTTP status codes occured. Status active or inactive for UDP data records Select a Provider status: Active or Inactive. The active status is selected by default. The status you select here defines whether the data record for the usage data provider is active or inactive. The status is used to filter records. The default filtering in eUsage is to show all records with active provider status, instead of basing this on the harvesting status. If you select the inactive option, for example because the provider no longer provides statistics, but you still want to keep the data, eUsage checks this status with the selected harvesting status. This means that you cannot have an inactive provider status if the harvesting status is still active. In this case, eUsage will offer you options. Status active or inactive within UDP data records Search filter for status of UDP data record Integration of a Month picker New Month picker component based on stripes Month picker within the section to exporting statistics Month picker within the harvest configuration of a UDP Others New order of UI elements within the edit mode of a UDP. On the one hand, the input sequence is more logical, and on the other hand, a feature should be added in the future that checks the credentials after the data has been entered and which reports are offered by the provider. SUSHI API is now called COUNTER API. The name is to be used from version Counter Release 5 onwards. For this reason, the text has been updated in various places in the user interface. Usage data provider (Edit mode): Information box next to the service URL input field. The info box explains how to enter the service URL. Additional technical requirements	Counter 5.1 Support https://folio-org.atlassian.net/browse/UXPROD-5300 Manual upload of Counter reports https://folio-org.atlassian.net/browse/UXPROD-5186 https://folio-org.atlassian.net/browse/UIEUS-421 https://folio-org.atlassian.net/browse/UXPROD-2926 Exception handling https://folio-org.atlassian.net/browse/UXPROD-5449 https://folio-org.atlassian.net/browse/UXPROD-5252 https://folio-org.atlassian.net/browse/UXPROD-4962 Status active or inactive for UDP data records https://folio-org.atlassian.net/browse/UXPROD-5084 https://folio-org.atlassian.net/browse/UXPROD-5292 https://folio-org.atlassian.net/browse/UXPROD-5085 https://folio-org.atlassian.net/browse/UIEUS-450 Month picker https://folio-org.atlassian.net/browse/UIEUS-420 https://folio-org.atlassian.net/browse/UXPROD-5465 https://folio-org.atlassian.net/browse/UXPROD-5287 Others https://folio-org.atlassian.net/browse/UXPROD-5288 https://folio-org.atlassian.net/browse/UXPROD-5495 https://folio-org.atlassian.net/browse/UXPROD-5506 https://folio-org.atlassian.net/browse/UXPROD-5771	@Stefan Dombek
Circulation apps - Workflow For use at location	With the new development of For use at location (reading room circulation) workflow, patrons can use certain items within the library. These items are typically stored in closed stacks. Patrons can request these items, which are then delivered to a designated staff area for use at the location. This new work covers changes in: Requests app Modify the create / edit requests form to include item loan type Add a flag to the request indicating that it is a For use at location request Suppress the option for a patron to request delivery at home address Check-out. The item is checked in at Service point The request is moved to “Open - awaiting pick up” status The item is checked out to the requesting patron The loan is defined as For use at location The open loan record is updated The circulation log is updated On the user record the loans which are for use at location are clearly identified Check-in. The staff member is allowed to select if the item should remain on hold or be returned to the shelves Service point settings will include a new setting for the default action to take A drop-down will be added to Check-in to allow users to change the check-in action options: Keep on hold shelf Close loan and return item Ask for action: A modal is displayed asking which of the above two actions should be taken Add “Default check-in action for use at location” to service point settings Add a For use at location option to the loan policy form	https://folio-org.atlassian.net/browse/UXPROD-1835 https://folio-org.atlassian.net/browse/UXPROD-4961 https://folio-org.atlassian.net/browse/UXPROD-5032 https://folio-org.atlassian.net/browse/UXPROD-5033 https://folio-org.atlassian.net/browse/UXPROD-5036 https://folio-org.atlassian.net/browse/UXPROD-5037 https://folio-org.atlassian.net/browse/UXPROD-5038 https://folio-org.atlassian.net/browse/UXPROD-5388 https://folio-org.atlassian.net/browse/UXPROD-5590 Other:	@Charlotte Whitt
Patron notices	To support e.g. the new work on For use at location, then a new patron notice token for Series statements has been added to all staff slips, and the staff slip editor has been expanded to allow for more complex layouts using Basic HTML tagging - read more here.	https://folio-org.atlassian.net/browse/UXPROD-5153 https://folio-org.atlassian.net/browse/UXPROD-5250	@Charlotte Whitt
Requests	Through Discovery (Locate or other systems via edge-api), third party resource sharing (formerly ECS) and FOLIO only resource sharing environment users (formerly LOC)* can now place a request for multiple parts of an multipart monograph or serial with one request, rather than placing a series of individual requests for each part. FOLIO receives these “batched” requests and processes them as individual item requests. The remainder of the request process and patron notices remain unchanged. *Single institution environment configuration work is ongoing and will be release when possible.	https://folio-org.atlassian.net/browse/UXPROD-5398