(URM-103876) Automatic Cleanup of Temporary Location After Restore Request

• The following 2 updates in the OLH were reviewed by Rivka (Yedidia is away)
• Update the following sections in Scanning Items:
  • Where it says: " It does not remove the value in the item's Temporary Location field."
    Update to "It removes the value in the item's Temporary Location field. Note that this is dependent on the force_empty_temp_location_when_disabled parameter (Configuration > Fulfillment > General > Other Settings)."
• Update Configuring Fulfillment Jobs:
  • Add the parameter "force_empty_temp_location_when_disabled". 
    Description:
    If set to true, when the Item is in temporary location radio button is set to no, no data will appear in the Temp Location field.
  • Rivka to reply to "To check in the code for (URM-103876) Automatic Cleanup of Temporary Location After Restore Request" to be sure the description is correct i.e., it was implemented like that in the code by Yedidia.

May 2026 Fulfillment and Resource Sharing Idea Exchange URM-103876 URM-103876

When an item is assigned a temporary location, one option for returning it to its permanent location is to process a Restore Request. Previously, after fulfilling a Restore Request, the temporary location flag on the item was correctly set to No, but the temporary location field still displayed the old temporary location value. With this enhancement, once a Restore Request is fulfilled, the temporary location field is automatically cleared, fully restoring the item’s location status and preventing confusion about its real location.

This behavior is controlled by the force_empty_temp_location_when_disabled parameter (Configuration > Fulfillment > General > Other Settings). It is true by default, and customers will need to set it to false to return to the previous behavior. Note, however, that for existing customers, this parameter is set to false.

For more information, see Scanning Items.

(URM-180322) Enhancements for Hold Requests

May 2026 Fulfillment and Resource Sharing Idea Exchange URM-103876 URM-180322

• Tzofiya said this will move to July unless there is a last minute change but unlikely
• Schedule a meeting with Tzofiya
• Managing the Hold Shelf - Ex Libris Knowledge Center
  • Where it says "If the patron fails to pick up the item by the expiration date:"
    • Add "A fine/fee may be charged for not picking up the item, based on fulfillment policies"
• Configuring Physical Fulfillment - Ex Libris Knowledge Center (Update per URM-180322 - Fine for On Hold Shelf Items not picked up - EXL - URM - Confluence)
• https://knowledge.exlibrisgroup.com/...rs_fulfillment 

The following enhancements were implemented for hold requests:

Configurable Purged Request Fee for Hold Requests
A new Purged Request Fee can now be configured in the Hold Request Terms of Use (TOU), similar to the existing option for booking requests. When staff process expired holds from the hold shelf using Reshelve, Transit, or Activate Next, the system consults the Hold Request TOU and automatically applies the appropriate fee. This gives libraries more precise control over cost recovery and ensures consistent handling of expired hold requests.

Control Over Canceling Hold Requests in Transit
A new circulation policy now allows libraries to determine whether a hold request can be canceled once it has been put in transit. This added control helps prevent unintended cancellations during fulfillment, strengthens workflow reliability, and ensures that items already en route continue through the process as intended.

For more information, see Managing the Hold Shelf, How to Set Up Requesting Policies and Configuring Fulfillment Jobs.

(URM-145473)Digitization Request Queue Indicator

May 2026 Fulfillment and Resource Sharing Idea Exchange URM-103876 URM-145473

• Review with Asaf Peter
• Digitization Processing - Ex Libris Knowledge Center
• Post-Receiving Processing - Ex Libris Knowledge Center?
• Working with Items - Ex Libris Knowledge Center?

Manage In‑Process Items now highlights when an item has additional digitization requests waiting in the queue. Staff can use a new row action to complete the current active digitization request and automatically activate the next one, improving workflow efficiency and ensuring queued digitization work progresses smoothly.

For more information, see Digitization Processing.

(URM-253329) Additional Information in Resource Sharing Directory Members API

The Resource Sharing Directory Members API has been enhanced to include the directory member's email and phone number.

(URM-320851 URM-323964 URM-326240) Improved Use of Network Resources in Course Reading Lists

May 2026 Fulfillment and Resource Sharing  Idea Exchange URM-320851 URM-323964 URM-326240

• Reviewed with Baruch
• OLH
  • Managing Citations - Ex Libris Knowledge Center
    • Where it says "The citation tabs in each row are:" add a new row to show that Hold By appears for Network Zone resources that are used in a citation.
    • In the "Adding a Citation Already in the Repository" section where it says "Search for a title; see Searching in Alma.", add also something like "Note that the search can also be done in the scope of the network zone." 
  • Searching in Alma
    • Tzofiya to reply to "Question about (URM-320851 URM-323964 URM-326240) Improved Use of Network Resources in Course Reading Lists" (originally was to Shoshana but she said its for Tzofiya and added her to the thread)

Institutions can now add resources from the Network Zone directly to locally managed reading lists. When a Network Zone resource is used in a citation, the reading list will display its availability across the consortium, including Held By information for all participating libraries.

This enhancement streamlines course support and improves visibility into shared network holdings.

For more information, see Searching in Alma and Managing Citations.

(URM-XXXXXX) TBD - Headline

TBD

For more information, see TBD.