How INN-Reach Converts a Same-server Request to a Local Hold
An INN-Reach request is considered "same-server" if the requested item is locally available to the patron; that is, both the owning site and patron site belong to the same Local Server, and the patron could request the item using the local catalog. The system manages a same-server request as an INN-Reach request from the point of request (the patron submits the request) to the point of fulfillment (the owning site checks out the item to the patron site). When the owning site checks out the item to the patron site, the system converts the INN-Reach request to a local circulation hold. Specifically, it:
- Removes the virtual record fields from the patron and item records.
- Removes the INN-Reach message field from the item record.
- Reformats the HOLD fields in the patron and item records as local circulation holds.
- Inserts a "transit" message note in the item record.
- Generates an item paging slip for the item, rather than an INN-Reach paging slip.
- Updates the following fixed-length fields in the item record:
| Field: | Updated to: |
|---|---|
| STATUS | 't' (IN TRANSIT) |
| DUE DATE | <blank> |
Multiple patrons can be associated with a same-server INN-Reach request if more than one patron from the same Local Server requests the same item. When the INN-Reach Central Server removes the virtual item from the first patron record, it moves the virtual item to the second patron record.
After the conversion, the system processes the item as if it were any standard circulation transaction. For information on how the system processes the item when it is checked in by staff at the pickup location, see Checking In an Item that Can Satisfy a Hold.
Any notices that the system generates for the item are standard circulation notices.
Converting Pickup Anywhere Requests
If an item that satisfies a Pickup Anywhere request belongs to the same Local Server as the patron who placed the request, the system converts the INN-Reach request to a local hold. However, in order for the system to communicate the necessary information to the pickup location, which might not be on the same Local Server, the item must still be handled as a Pickup Anywhere item. For example, the pickup location must check in the request using the Pickup Anywhere - Receive Items function. For information, see Circulating Pickup Anywhere Items.