Thanks, Kathy and Jason for your comments. Thinking about what you've said about stalling. We get the idea that op capture is the least costly way to fill a hold, since the item is already in the hands of a staff person, and may already be at the pickup location. If you're trying to reduce transits around the system, wouldn't you want to delay having the hold appear on a pull list to give the op capture a chance to fill the hold?
Regards, June -----Original Message----- From: open-ils-general-boun...@list.georgialibraries.org [mailto:open-ils-general-boun...@list.georgialibraries.org] On Behalf Of Kathy Lussier Sent: Thursday, January 13, 2011 9:50 AM To: 'Evergreen Discussion Group' Subject: Re: [OPEN-ILS-GENERAL] Holds settings in Evergreen > Does that make sense? Yes, your explanation cleared up a lot of questions I had about holds stalling. Thanks Jason! Kathy ------------------------------------------------------------- Kathy Lussier Project Coordinator Massachusetts Library Network Cooperative (508) 756-0172 (508) 755-3721 (fax) kluss...@masslnc.org IM: kmlussier (AOL & Yahoo) Twitter: http://www.twitter.com/kmlussier > -----Original Message----- > From: open-ils-general-boun...@list.georgialibraries.org > [mailto:open-ils-general-boun...@list.georgialibraries.org] > On Behalf Of Jason Etheridge > Sent: Wednesday, January 12, 2011 5:47 PM > To: Evergreen Discussion Group > Subject: Re: [OPEN-ILS-GENERAL] ***SPAM*** RE: Holds settings > in Evergreen > > On Wed, Jan 12, 2011 at 5:37 PM, Kathy Lussier > <kluss...@masslnc.org> wrote: > > Thank you for the response Jason. I knew that stalling only > impacted > > opportunistic holds captures, but the fact that it stalls > one process > > and not the other confuses me about what the ultimate > intent of the setting is. > > Kathy, > > So I've mentioned 2 libraries in my scenario, the pickup lib > and the "pull" lib. Now imagine if opportunistic capture was > enabled and you have 270+ libraries in your consortium. > Staff at the pull lib may very well go to the trouble of > pulling a targeted item, only to find that the hold it was > being pulled for has already opportunistically captured > another eligible item that was checked in at one of the other > 269+ libraries. This is okay if it's the pickup lib doing the > capturing (yay for the patron getting it sooner), but staff > at the pull lib could feel slighted, and staff at other libs > that happen to process their check-ins earlier in the morning > could also get slammed with the lions' share of hold captures. > > That's what hold stalling was trying to address. You got > picked to fulfill a hold, so we're giving you a chance to do > it, except in the case where the pickup comes across the > desired item sooner (saving ourselves a transit). > > Does that make sense? > > -- > Jason Etheridge > | VP, Tactical Development > | Equinox Software, Inc. / Your Library's Guide to Open Source > | phone: 1-877-OPEN-ILS (673-6457) > | email: ja...@esilibrary.com > | web: http://www.esilibrary.com >
