Jason, My understanding from someone who had done this is it does take precedence, or at least it did in 1.4. Some PINES libraries apparently used it often to bring items back once they were stuck supplying holds elsewhere.
Elaine J. Elaine Hardy PINES Bibliographic Projects and Metadata Manager Georgia Public Library Service, A Unit of the University System of Georgia 1800 Century Place, Suite 150 Atlanta, Ga. 30345-4304 404.235-7128 404.235-7201, fax [email protected] www.georgialibraries.org http://www.georgialibraries.org/pines/ -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jason Etheridge Sent: Wednesday, June 15, 2011 12:57 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Item "Recall" function? On Wed, Jun 15, 2011 at 12:44 PM, Hardy, Elaine <[email protected]> wrote: > I have not tried this, but it is my understanding that a workaround is > to place a copy level hold on the specific item you want returned to > the owning library. That should act as if it were a recall and bring > the item back to the owning/circulating library that places the hold. The downside here is that I don't believe copy-level holds take precedence over other hold types. However, you could use the Top of Queue (cut-in-line) function on a given hold. In 2.1, you can also set up hold priority based on user profile. I think notifying the person with the item is one of the big features of recalls. I totally missed that this was implemented in 2.1. dbs++ et al -- Jason Etheridge | VP, Tactical Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com Equinox is going to New Orleans! Please visit us at booth 550 at ALA Annual to learn more about Koha and Evergreen.
