[Koha-bugs] [Bug 17593] New: Extend circulation rules to include shelving location
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Wed Nov 9 12:45:56 CET 2016
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17593
Bug ID: 17593
Summary: Extend circulation rules to include shelving location
Change sponsored?: ---
Product: Koha
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Circulation
Assignee: koha-bugs at lists.koha-community.org
Reporter: stefan.berndtsson at ub.gu.se
QA Contact: testopia at bugs.koha-community.org
CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com
We are in the process of moving over to Koha, and are still trying to manage
all the details around this. Circulation rules are a big thing we have to
tackle here.
At the moment, we have multiple libraries, and within each library we have both
open and closed stacks as well as multiple other segmentations, all specified
as shelving locations (authorized value LOC).
These locations are not always governed by the same set of rules, so it would
be very helpful if the system could support LOC as a circulation rule condition
alongside library, patron category and item type.
>From doing a fairly brief look at the code, it seems GetIssuingRule and
GetLoanLength in C4/Circulation.pm are the main points where the ruleset is
retreived. There will of course be all the places calling these two functions,
as well as database management parts to consider.
If we were to develop some sort of extension to these rules, what would be an
appropriate approach? It should certainly be an option to turn on to be used,
but should we consider LOC as a starting point, or should LOC just be one many
possible choices in the configuration?
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list