[OPEN-ILS-GENERAL] Floating Collections

[Tim Spindler]

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.


Tim

On Wed, Aug 8, 2012 at 9:54 AM, Jason Stephenson <jstephenson at mvlc.org>wrote:

> Quoting Bill Ott <bott at grpl.org>:
>
>  We ran into the same issue, but because we only want collections to float
>> to/from certain locations.  The following is how we handled it in the
>> short-term.  Basically, ignoring "floating" unless it was within a short
>> list of org units.
>>
>>
>> https://github.com/grpl-eg/**rel_2_1/commit/**
>> eee5b7b11154e1918cda13e67ef0d1**f0a6a1b846#lib/Application/**
>> Circ/Circulate.pm<https://github.com/grpl-eg/rel_2_1/commit/eee5b7b11154e1918cda13e67ef0d1f0a6a1b846#lib/Application/Circ/Circulate.pm>
>>
>
> While a hack like the above works for 1 Evergreen installation, I think if
> enough different Evergreen users want this, then they should get together
> and work out a specification that could be implemented in Evergreen for
> everyone.
>
> I can think of different ways to implement this depending on the desired
> level of flexibility.
>
> --
> Jason Stephenson
> Assistant Director for Technology Services
> Merrimack Valley Library Consortium
> Chief Bug Wrangler, Evergreen ILS
>



-- 
Tim Spindler
tjspindler at gmail.com

*P**   Go Green - **Save a tree! Please don't print this e-mail unless it's
really necessary.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20120808/e1f9068c/attachment-0001.htm>