[OPEN-ILS-DEV] Holds Prioritization Development

[Jason Etheridge]

> A hard boundary just says, "never go past here", and a soft boundary
> says, "if there's a potential item within the boundary, never look
> outside the boundary" (and this never gets re-evaluated, so if the
> potential item disappears, you're stuck).

Actually, that soft boundary description isn't _quite_ right.  The
effective "boundary" can shrink once a potential item is found.
What's actually happening is the selection depth is changing.

So let's say there's an eligible item checked out at the hold's pickup
lib, and the software boundary is set to System (assuming a stock
Consortium -> System -> Branch hierarchy).  Since the potential item
is at depth greater than or equal to the setting, the selection depth
of the hold will be set to match the item, at Branch, in hopes of
eventually getting that checked out item.  It'll never look past the
pick up library at that point.

I don't really like soft boundaries. :-)

-- 
Jason Etheridge
 | Equinox Software, Inc. / The Open Source Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  jason at esilibrary.com
 | web:  http://www.esilibrary.com
 | Supporting Koha and Evergreen: http://koha-community.org &
http://evergreen-ils.org