Settings and activity
366 results found
-
2 votes
Lynn Reynish supported this idea ·
-
2 votes
Lynn Reynish supported this idea ·
-
14 votes
An error occurred while saving the comment -
3 votes
Lynn Reynish supported this idea ·
-
8 votes
Lynn Reynish supported this idea ·
-
3 votes
Lynn Reynish supported this idea ·
-
3 votesUNDER REVIEW · 0 comments · ILS - Polaris » Acquisitions, Serials & Item/Issue/Inventory Management · Admin →
Lynn Reynish supported this idea ·
-
5 votes
Lynn Reynish supported this idea ·
-
4 votes
Lynn Reynish supported this idea ·
-
8 votes
Lynn Reynish supported this idea ·
-
7 votes
Lynn Reynish supported this idea ·
-
24 votes
Lynn Reynish supported this idea ·
-
7 votes
Lynn Reynish supported this idea ·
-
18 votes
Lynn Reynish supported this idea ·
-
11 votes
Lynn Reynish supported this idea ·
-
4 votes
Lynn Reynish supported this idea ·
-
6 votes
Lynn Reynish supported this idea ·
-
3 votes
Lynn Reynish supported this idea ·
-
17 votes
Lynn Reynish supported this idea ·
-
13 votes
Lynn Reynish supported this idea ·
I'm curious about how your Holds Routing Sequences are set up because our consortium is set up such that it prioritizes local items to fill the request first in the primary holds routing sequence before moving on to the secondary routing sequence. I'm just a local admin at a member library (not at the consortium) but I can tell you what I see:
Our Primary Routing Sequence consists of just our branches. The order that each branch pulls from is individualized to the branch. Our Secondary Routing Sequence starts with our branches and then moves on to the rest of the consortium. The other consortium library systems are in an order we specify.
We also use the item record setting "Limit to: Patrons from this library and branches - x days past first available" for all newly added items.
Those allow us to prioritize local holds and reduce shipping.