Hold Options Dialog Box - RTF Tab

Use this dialog box to control requests-to-fill (RTF Requests-To-Fill or RTF processing sends hold requests to designated libraries in a specified order. A library chooses to fill or deny the request. The request is routed until it is filled, it expires, or every library denies it.) processing by setting the following options:

Note:

For more information on holds routing and setting up primary and secondary RTF routes, see Setting Up Holds Routing.

• Allow only one cycle in Primary RTF - Select to send requests through the RTF cycle only once when all libraries in the requester branch’s primary routing table deny or ignore the request. When this option is checked and you use only one routing sequence, at the end, the request status becomes Active and the item can be trapped An item is said to be trapped for a hold when an item that fills a request is scanned at circulation and the system links the item to a specific request, either automatically or by displaying a message that prompts you for a decision. at circulation, but the request no longer appears on the responder libraries’ RTF lists. If you use a primary and secondary routing sequence, the request goes to the secondary routing sequence at the end of the cycle. The setting overrides your setting for Total Days in Primary RTF cycle on this tab when all responder libraries deny or ignore the request.
• Allow only one cycle in Secondary RTF sequence (for libraries that use secondary routing sequences.) - Select to send requests through the secondary RTF cycle only once when all libraries in the requester branch’s secondary routing table deny or ignore the request. When this option is checked, at the end of the secondary routing cycle, the request status becomes Active, and the item can be trapped at circulation, but the request no longer appears on the libraries’ RTF lists. The setting overrides your setting for Total Days in Secondary RTF cycle on this tab when all secondary responder libraries deny or ignore the request.
• Randomize Primary RTF Responder - Select to have the system randomly select which library in the primary RTF sequence is the next library to get the request when the first branch in the sequence denies or ignores the request. After Polaris selects the next library, the sequence is followed in order. You might select this option to prevent the same library from repeatedly filling the requester branch’s requests.
• Randomize Secondary RTF Responder (for libraries that use secondary routing sequences) - Select to have the system randomly select which library in the secondary RTF sequence is the next library to get the request when the first branch in the specified start sequence denies or ignores the request. This option works like Randomize Primary RTF Responder (above), but it applies to the secondary routing sequence.
• When no items in Primary RTF transfer immediately (for libraries that use secondary routing sequences) - Select to send a request immediately to the secondary routing sequence when no items are In at any of the responder branches in the primary routing sequence. If this option is not selected, the request remains in the primary group for the period you set in Total Days in Primary RTF cycle, regardless of whether there are no In items left to process or all primary libraries have denied or ignored the request.
• Time out Located status - Select the box and specify the number of hours a request can remain in a Located status before it reverts to a Pending status.

Note:
The Located status is assigned only through the Leap Picklist. It indicates that an item was found to fill a request, but it has not been checked in to trap. If the Time out Located status box is checked and a time period is set for the pickup library, requests that remain in a Located status for the specified time period revert to a status of Pending.

• Total Days in Primary RTF cycle - Type the number of days a hold request continues to follow the sequence of responder branches designated in the Holds Routing Sequences Primary policy table (see Setting Up Holds Routing). When this time period is over, the request can still be filled when an item is trapped at circulation, but it is no longer routed to the branches.
• Total Days in Secondary RTF cycle (for libraries that use secondary routing sequences) - Type the number of days a hold request continues to follow the sequence of responder branches, as designated in the Holds Routing Sequences Secondary policy table (see Setting Up Holds Routing). When this time period is over, the request can still be filled when an item is trapped at circulation, but it is no longer routed to the branches.
• Default not-supplied reason (system level only) - Select the default reason that is displayed when a library denies a hold request. Your choices for this setting are defined in the User Defined Hold Not Supplied Reasons policy table. See Defining Not-Supplied Reasons.
•  If all material limits are exceeded set to Not Supplied - Select this option to display a block message in the staff client when all the items attached to the bibliographic record have the same material type and a patron has reached the hold limit by material type. The system uses the setting of the governing library for patron blocks.

Note:
When this option is checked and the block is overridden, the request is placed with a status of Not Supplied. The Not Supplied reason is All items denied by system. If some items have the limited material type and some do not, a message is displayed and those of the limited material type are automatically denied by the system.
If this option is not checked, and all the items attached to the bibliographic record have the same material type, the block message is displayed in the staff client as above. However, if the block is overridden, the request is placed with a status of Active. If some items have the limited material type and some do not, a message is displayed and those of the limited material type are automatically denied by the system.