[OPEN-ILS-GENERAL] Floating Collections

Jason Stephenson jstephenson at mvlc.org
Wed Aug 8 10:04:59 EDT 2012


Quoting Tim Spindler <tjspindler at gmail.com>:

> For us, we only have really one library that wants this and if it was
> controlled by org units (system level) then it would be fine for our
> purpose.  Essentially, no copy could float outside a given set of org
> units.  I guess this could be defined by the hierarchy.  However, I'm sure
> there are other ways it could be used.

If it were based on the hierarchy, a float_level or something similar  
could be specified either on copies or as an org unit setting. This  
would then correspond to a level in the hierarchy where that copy or  
org unit copies would float: Consortium, System, Branch (would include  
sub-libraries). Basically at that hierarchy level or below.

To accommodate floating between arbitrary org units, you'd need  
something like a float group created to specify that copies float  
among these specific org units.

The former would fit better with Evergreen's current modus operandi  
and would likely be easier to implement. The latter would offer more  
flexibility at the cost of some complication.



-- 
Jason Stephenson
Assistant Director for Technology Services
Merrimack Valley Library Consortium
Chief Bug Wrangler, Evergreen ILS


More information about the Open-ils-general mailing list