Hi Mike,
Oh that's quite interesting. I had forgotten about that blog post, but
now in reviewing it, it does sound like it could potentially solve the
situation I'm describing.
How far along are the plans to port features from Fulfillment to
Evergreen? Maybe something that we could help to test in the future.
-- Ben
On 07/30/2012 01:17 PM, Mike Rylander wrote:
On Mon, Jul 30, 2012 at 12:32 PM, Ben Shum <bs...@biblio.org> wrote:
Hi folks,
So here's a situation. A library system has multiple branches, and each
owns their own copies/patrons. Library A owns a copy of an item and Library
B does not. But patrons from both A and B place holds against the material.
Because of how holds target / opportunistically capture, the patrons at
Library A receive the item first while the item continues to circulate in
and out of Library A, while the patrons at Library B never get their holds
fulfilled. It would be preferred that Library A's copy be used to fill
holds for both Library A and B's patrons in the order the hold was placed
regardless of pickup location.
While we understand that having additional copies for each branch could
solve the issue, it may not be possible for the library to purchase and
assign copies to each branch. Instead, they're hoping that it is possible
to re-prioritize holds within their system to follow a stricter first-in,
first-out (FIFO) policy. However, the concern has been made as to how FIFO
might adversely alter how the library system shares material with the rest
of the consortium.
Does anyone have any suggestions about other solutions or are we looking at
some sort of development to change how holds target within different groups?
The Custom Best-hold Selection Order part of
http://blog.esilibrary.com/2012/04/16/sharing-code-is-caring/ would
handle that, if I understand correctly what it is you want to do.
--
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113
