Trillium R1 2026 Notes on functionality

Trillium R1 2026 Notes on functionality

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

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

 

Requests

Request anonymization has NOT been implemented and is not ready for use. However new capabilities and an API endpoint have been created. These will not be functional with Trillium. The feature work will be completed in Umbrellaleaf

New Data Capabilites:

  • app-platform-complete - Circulation Request-Anonymization-Settings (View, Edit)

  • app-platform-complete - Circulation Requests Anonymize Item (Create)

  • app-platform-complete - Modperms Circulation Request-Anonymization-Settings (View, Edit)

New API Endpoint:

  • /request-anonymization/{request UUID}

https://folio-org.atlassian.net/browse/UXPROD-4302

@Amelia Sutton