[OPEN-ILS-DEV] ***SPAM*** Meaning of a couple of fields in action.hold_request

[Mike Rylander]

On Wed, Jul 21, 2010 at 12:39 AM, Jason Etheridge <jason at esilibrary.com> wrote:
> On Tue, Jul 20, 2010 at 11:45 PM, John Craig
> <jc-mailinglist at alphagconsulting.com> wrote:
>> selection_ou
>
> In practice, this is the same as the pickup library, but can be
> different if you set it to be different in the staff client.  It is
> the library at which the hold targeter starts to look for eligible
> copies for the hold.  So all else being equal, an item at the pickup
> library will be grabbed for a hold before an item elsewhere.

Scratch that last sentence.  Capture (what "grabbed" sounds like to
me) is completely orthogonal to the process of finding potential
copies, and even orthogonal to targetting.

>
>> selection_depth
>
> And this is how far from the selection_ou the hold targeter is willing
> to look, in terms of the org hierarchy.  If the depth is 0, that's the
> top of the hierarchy, so the targeter will examine the entire
> consortium if need be.
>
> Assuming a stock hierarchy of
> 0 - Consortium
> 1 - System
> 2 - Branch
>
> Then a selection depth of 1 will have the targeter looking at every
> branch in the system, after it looks at the selection ou first.  If
> the selection depth is 2, then the targeter will never look beyond the
> branch (the selection ou).
>
> By default, holds placed in Evergreen get a selection depth of 0.
> There are some (or at least one) org unit settings that can affect
> this.
>

Both of the hold boundary settings can effect this.

-- 
Mike Rylander
 | VP, Research and Design
 | Equinox Software, Inc. / The Evergreen Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com