Predefined Routes Table
To view circulation parameters, you must be assigned permission 373 (View Circulation Parameters). To edit the Predefined Routes table, you must be assigned permission 383 (Edit Predefined Routes). See Permissions Used by Sierra for more information.
Libraries that have acquired Mobile Collections can use the Predefined Routes table to set up routes that are commonly used to transport collections between locations. The system uses this table when you assign a route to a collection.
You can access the Predefined Routes table via the following menu path:
Admin | Parameters | Circulation | Predefined Routes
For information on modifying this table, see Maintaining System Parameter Tables and Maintaining Circulation Parameters.
For more information, see Functionality Information and Data Elements.
Functionality Information
When viewing and modifying the Predefined Routes table, note the following:
Maximum Number of Entries
The Predefined Routes table can contain a maximum of 1,500 entries.
Changes Are Not Retroactive
Changes to entries in the Predefined Routes table do not affect collections to which the route has already been assigned. If you want to change an existing collection's route, you must edit the collection's route.
Data Elements
Entries in the Predefined Routes table contain the following data elements:
Element |
Description |
Route Name |
A descriptive label for the route (maximum of 30 characters). |
Route Table |
The Route table contains two elements: Location and Days.
The Location column contains locations from the Branches table to which to transfer the collection. Each predefined route can contain a maximum of 300 locations.
The Days column specifies the number of days that the collection remains at each location.
|