[Evergreen-general] Hold Policies: Transit Range & Range is from Owning Lib

[Morgan, Michele]

Hi Benjamin,

Our consortium shares resources heavily. We do not have many hold policies
in place since, by default, everything is holdable everywhere.

For items and collections that are not holdable at all, we generally set
the Holdable flag to False in Shelving Locations or items themselves rather
than using a hold policy.

Hold Policies only come into play in our consortium when different behavior
is needed for different patron permission groups, or when we need to
restrict  items to local pickup for holds.

For example, for a given library's "Library of Things" we use a circ
modifier and have a policy for that circ modifier, specifying the item circ
library and a transit range of System.

We don't have any rules that have transit range set to the consortium since
that is true by default.

Hope this is helpful!

Michele

--
Michele M. Morgan, Systems Support Specialist
North of Boston Library Exchange, Danvers Massachusetts
mmorgan at noblenet.org



On Thu, May 25, 2023 at 9:42 AM Jason Boyer via Evergreen-general <
evergreen-general at list.evergreen-ils.org> wrote:

> Hi Benjamin, others may be able to give additional details, but the
> Transit Range is used to determine how "far" an item could potentially
> travel from its circ_lib to the pickup_ou for that hold policy to apply. So
> if a policy has a transit range of 2, that policy only matches if a copy
> would be sent from 1 branch to another in the same system. That "distance"
> is up one to the system, then down one to the other branch(es). That policy
> would not match for items from other systems though because that distance
> would be 4 (1 up to the parent system, 1 up to the parent (likely cons), 1
> down to a neighboring system, and finally 1 down to a branch), so you could
> use transit range to change other values based on item proximity. Maybe
> users are allowed to have a higher number of holds on items within a single
> system because shipping would be cheaper or something like that. I've never
> tried to set things up that way so don't necessarily take that as an
> endorsement. :D
>
> "Range is from Owning Lib" just means to do that distance calculation
> against the item's call number owning_ou instead of the item's circ_lib, in
> case floating is used in your consortium. When floating is in use an item's
> circ_lib is wherever it was returned, but the owning_ou may be different
> because it's the purchasing location.
>
> Jason
>
> --
> Jason Boyer
> Senior System Administrator
> Equinox Open Library Initiative
> JBoyer at equinoxOLI.org
> +1 (877) Open-ILS (673-6457)
> https://equinoxOLI.org/
>
> On May 25, 2023, at 8:44 AM, Murphy, Benjamin via Evergreen-general <
> evergreen-general at list.evergreen-ils.org> wrote:
>
> Hello hivemind,
>
> I'm trying to understand how exactly Transit Range & Range is from Owning
> Lib settings are meant to work in hold policies. I didn't find anything in
> the documentation about these settings.
>
> Should any policy that's meant to be part of what allows things to
> resource share have a Transit Range = Consortium and local policies that
> provide system level access to non-resource sharing materials have a
> Transit Range = System?
>
> How is Range is from Owning Lib meant to be used? Is it really only used
> for System or Branch limiting policies? Do you know of an example of when
> it might be used?
>
>
> More detail on our typical configurations is it is helpful:
>
> In general, we differentiate most of our hold policies by Pickup Lib. Our
> weights are:
>
> User Perm = 18
> Requestor Perm = 2
> Circ Mod = 10
> Pickup Lib = 10
> Owning Lib = 10
> User Home Lib = 8
> Request Lib = 8
>
> We have a few high level blocking policies by circ mod (things that don't
> resource share in the consortium) as well as a few high level allow
> policies for the circ mods that do resource share. Then individual library
> systems have allow policies for resource sharing and blocking policies for
> all sorts of materials generally defined by:
>
> Pickup Lib = System
> User Home Lib = Consortium
> Request Lib = Consortium
> Owning Lib = Consortium
>
> We then also have local allow policies for non-resource sharing things
> available within the system level set up like:
>
> Pickup Lib = System
> User Home Lib = System
> Request Lib = System
> Owning Lib = System
>
> Then branch specific policies are sort of case dependent and rare.
>
>
> *Benjamin Murphy*
> NC Cardinal Program Manager
> State Library of North Carolina
> *benjamin.murphy at ncdcr.gov <benjamin.murphy at ncdcr.gov> * |
> https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal
> 109 East Jones Street  | 4640 Mail Service Center
> Raleigh, North Carolina 27699-4600
>
> The State Library is part of the NC Department of Natural & Cultural
> Resources.
> *Email correspondence to and from this address is subject to the North
> Carolina Public Records Law and may be disclosed to third parties.*
>
>
>
> _______________________________________________
> Evergreen-general mailing list
> Evergreen-general at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
>
> _______________________________________________
> Evergreen-general mailing list
> Evergreen-general at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-general/attachments/20230525/c364d071/attachment-0001.htm>