Fulfillment - Trillium - Notes on functionality
UXPROD-5499 - Prevent Inactive patrons from submitting requests (FOLIO ECS Circulation)
Within FOLIO ECS Circulation, Inactive patrons should not be able to create Requests. When a Patron account is marked as Inactive on their primary User account, that information needs to ensure the prevention of any Request creation in this environment.
Related to Requests app attempts:
In Scope
When any Request app creation workflow is triggered, validate the requester
The requester’s status must be Active
If the requester is Inactive, the process must stop and return an error
When any Mediated request app workflow (Save or Confirm) is triggered, validate the requester
The requester’s status must be Active
If the requester is Inactive, the process must stop and return an error
Note: Work completed in Trillium, and it is also available in R CSP #6 and S CSP #6.
One patron request for multiple items of a multipart monograph or serial
UXPROD-5398
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. This significantly improves the workflow for patrons when they request more than a few parts/volumes/issues of the same title at a time.
*Please see UXPROD-5827 for single institution environment configuration work.
UXPROD-5261 - Claimed returned functionality (FOLIO ECS Circulation)
Just like in FOLIO Circulation libraries, staff in a FOLIO ECS Circulation setup need to be able to mark an item as Claimed Returned when a patron says they brought it back but the system shows no return. Because items and loans can belong to different tenants in an ECS environment, the consortium needs a shared, accurate record of what happened.
What needs to happen
When a patron claims they returned an item:
Loan status must update across all involved tenants (so every library sees the same loan information)
Item status must update across all involved tenants (so the item’s status is consistent everywhere)
This ensures the patron’s account reflects their claim and the Consortium has a unified view of the item’s status.
Note: Work completed in Trillium, and is also available by Sunflower CSP #2.
Declared lost after Claimed returned
Secure tenant related: Declared lost after claimed returned
Secure tenant related: Declared lost after claimed returned for collection with exclusive materials (e.g., Items can only be requested by Patrons with User records housed within that tenant)
UXPROD-5262 - Declared lost functionality (FOLIO ECS Circulation)
Just like in FOLIO Circulation libraries, staff in a FOLIO ECS Circulation setup need to be able to mark an item as Declared Lost when a patron says they can’t return it. Because items and loans may belong to different tenants in a consortium, everyone needs to see the same information about the item and the patron’s account.
What needs to happen
When an item is marked Declared Lost:
The loan status must update across all participating tenants (so every library sees the same loan information)
The item status must update across all participating tenants (so the item’s condition is consistent everywhere)
This ensures the patron’s record reflects their statement and the consortium has an accurate, shared view of the item’s status.
Declared lost
Secure tenant related: Declared lost
UXPROD-5468 - Resolve claimed returned: Mark missing functionality (FOLIO ECS Circulation)
Just like in FOLIO Circulation libraries, staff in an FOLIO ECS Circulation setup need to be able to mark an item as Missing when a patron says they returned it but the library can’t find it. Because the item and its loan may belong to different tenants in the consortium, everyone needs to see the same, up‑to‑date information.
In scope
When an item is marked Missing:
The loan status must update across all participating tenants (so every library sees the same loan record)
The item status must update across all participating tenants (so the item’s status is consistent everywhere)
This ensures the patron’s account reflects the situation and the consortium has a shared, accurate record of the item’s status.
See Comments of UIU-3444 for screencasts of functionality.
Note: Work completed in Trillium, and is also available by Sunflower CSP #2.
UXPROD-5485 - Search by Mediated request UUID
The Mediated Requests app now supports searching by Mediated Request UUID, bringing it in line with the search capabilities already available in the Requests app. This improvement helps staff quickly locate specific mediated requests without needing additional identifiers.
Why this matters
Library staff working with mediated requests often need to quickly retrieve a request. Previously, searching by Mediated request UUID was not possible, slowing down workflows and troubleshooting. With this enhancement, staff can efficiently search, locate, and manage Mediated requests through this additional option.
In Scope
Added the ability to search by Mediated Request UUID in the Mediated Requests app.
Supports Congressional Loan staff who also require UUID‑based searching.
See Comments of UIREQMED-112 for screencasts of functionality.