On Wed, Aug 8, 2012 at 10:04 AM, Jason Stephenson <[email protected]> wrote: > Quoting Tim Spindler <[email protected]>: > >> 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. > >
Just time for a quick note, but there's the lasso framework. It "works" for search, but isn't exposed currently (IIRC, and surely not in TPAC). I think that would work well as the basis for float-group. I have some further thoughts, including float-depth, but they're not fully formed ATM. I'll try to write something up soon-ish, but don't let that threat derail any further discussion. -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: [email protected] | web: http://www.esilibrary.com
