[Koha-bugs] [Bug 7144] Floating collection

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7144

Kyle M Hall <kyle.m.hall at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kyle.m.hall at gmail.com

--- Comment #26 from Kyle M Hall <kyle.m.hall at gmail.com> ---
Maybe I'm a bit late in asking this, but why use itemtype for the floating
collection rules instead of collection code? It seems odd to require a separate
item type for floating items that are really Books, Audiobooks, etc.

For example, at the Crawford County Federated Library System, there are a
number of 'rotating collections'. The books and audiobooks move from from one
library to the next each month. 

I have written a rotating collections feature for them that lets the
librarian's create 'collections' of items, and set what branch the collection
is currently at. Koha currently tracks who owns and item, and where an item is
at, but not where an item should be. For example, Collection1 is at LibraryA,
and is now to be moved to LibraryB. It my system, a librarian simply goes into
the rotating collections system and changes the current library for Collection1
from LibraryA to LibraryB. LibraryA then packs up all the items that are
currently on the shelf and ships them to LibraryB. When any books in
Collection1 that are currently circulating are checked in, the librarian
recieves a notice that the item is part of a rotating collection and should be
transferred to LibraryB immediately.

Could this feature be used to replicate this scenario? If not, I would be more
than happy to open a bug and submit my rotating collections code. I suppose
rotating collections are different than floating collections in how they
behave.

-- 
You are receiving this mail because:
You are watching all bug changes.