1.5. FIFO

FIFO

First In First Out
FIFO attempts to ensure that holds are filled in exact order placed
FIFO is excellent for smaller geographical areas
FIFO is also good for geographically dispersed consortia for which transit costs are not an issue
Don’t set FIFO at each branch; set FIFO at the top level of intended use.
If using Hard Boundaries, ensure they are set at the same level as FIFO.
(e.g. If Systems A and B don’t resource share, set FIFO at System A and System B. If they *do* resource share, set FIFO at the Consortia level.)
It is not recommended to use stalling in conjunction with FIFO as stalling restricts transiting. Using stalling and FIFO together will make it harder for Evergreen to fill holds and increase patron wait times.
FIFO cannot ever be “exact” order placed. When missing items are found and new items are added it changes the potentials list. The next group of holds to be targeted or retargeted will have the new items and therefore items not at the top of the queue might get an available hold sooner. Remember the potentials list (and therefore FIFO) is also affected by library closed dates.

This page was: Helpful | Not Helpful