Understanding Transit Holds

When a location checks in an item that has been requested at another location, Horizon changes the item’s status to “In Transit” and tells the staff member where to send the item. This item is then called a “transit hold.” By default, Horizon requires you to use this transit hold to fill the next hold request in the hold request queue, whether that request is local or remote. You can change this default and instead let your circulation staff fill a local open hold request with the first available item that is checked in at your location. You can also set up Horizon so that it tries to minimize the number of transit holds.

You can further limit transit holds so items outside of your location's primary location group are not used to fill a request under specific conditions. If your library has an item currently circulating that could fill the request, that item is requested when it is checked in rather than using an outside item. This feature can be used when transit times or cost of transits between groups make it preferable to wait for a local item to fill the hold.

Your library may occasionally use short non-standard item barcodes (those that are shorter than your system administrator has defined in the location view). If you modify and save any item barcodes on in-transit items, Horizon automatically pads or adds digits to equal the defined barcode length. When the items get to the new location, users or staff cannot search for them because the barcodes are invalid.

If you do not modify and save a barcode as you work with in-transit items, Horizon leaves short, non-standard barcodes as they are.

This section explains these topics:

 


© 1998-2017 Sirsi Corporation