On Wed, Jun 23, 2010 at 11:47 AM, Turner, Jennifer M <[email protected]> wrote: > Hello all, > > We have been testing the FIFO patch in version 1.6.0.5 and are having some > issues with implementation. We have FIFO set to ‘True’ at the system level > in Organization Unit Settings. However, when capturing an item for a hold > from a branch, the item is still sent to a patron at that branch, even if > patrons at other branches placed holds at an earlier date. > > Example: > An item has 17 holds on it. > Patron 1 placed a hold on 2010-02-18 at Branch X > Patron 2 placed a hold on 2010-02-19 at Branch X > Patron 3 placed a hold on 2010-02-21 at Branch Y > Patron 4 placed a hold on 2010-03-02 at Branch Z > (etc) > > The item is returned to branch Y. Patron 3 at Branch Y receives the item; > Patrons 1 and 2 are kept waiting. > > Do we need to set FIFO to ‘True’ at the branch level? Or is there another > configuration piece that we are missing?
In your example, branches X, Y and Z are all inside the system that has FIFO holds enabled? --miker -- Mike Rylander | VP, Research and Design | Equinox Software, Inc. / The Evergreen Experts | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
