https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24956 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@bugs.koha-c | |ommunity.org -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24956 Jason Robb <jrobb@sekls.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrobb@sekls.org --- Comment #1 from Jason Robb <jrobb@sekls.org> --- It would save a lot of time and headache if there were an override layer above the existing circ/fine rules setup. We heavily rely on an "All/All" rule at each branch to reduce the total number of rules needed to accommodate a fluctuating number of item types and patron categories. That works well, but it means if we need a rule that affects all branches, it requires a new rule line for each individual branch. As an example, we don't want self-registered patrons to be able to check out until they upgrade their account to a regular patron category. At the moment, every branch needs a SELFREG/All rule to prevent checkouts to the SELFREG category. If those rules aren't set, they'll hit the All/All rule for that branch before they can reach a SELFREG/All rule on the "Standard rules" setup. A global override rule would reduce the rules needed from one per branch to just one rule. Another possible implementation might be to make a "Global rule overrides for all libraries" page similar to the "Standard rules for all libraries" page, where any rules set on the overrides page would take top priority. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24956 --- Comment #2 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- At the moment the rule system is already complex, I'd warn against adding complexity needlessly. I believe what Jason described is a different use case to the temporary overwrite Nick suggested that would overwrite ALL existing rules with a new rule set temporarily. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24956 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cbrannon@cdalibrary.org --- Comment #3 from Christopher Brannon <cbrannon@cdalibrary.org> --- I would be interested in a way to override some or all rules without touching the original rules. Sounds like a great idea. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24956 Katie Bliss <kebliss@dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss@dmpl.org -- You are receiving this mail because: You are watching all bug changes.