Summary: | Changes to circ rules should be logged | ||
---|---|---|---|
Product: | Koha | Reporter: | Barton Chittenden <barton> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | barbara.johnson, bwsdonna, catrina, daniel.gaghan, dcook, george, gmcharlt, hebah, jheltibridle, jofsa, kbecker, kebliss, kelly, kyle.m.hall, lisette, lisettepalouse+koha, marie-luce.laflamme, marjorie.barry-vila, noemie.labine |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | |||
Bug Blocks: | 22794 |
Description
Barton Chittenden
2016-05-18 14:25:41 UTC
Changes to circ and fine rules should be logged for troubleshooting and accountability. Because we have the ability to completely overwrite a library's lending rules using the clone feature, a backup/log should be kept. *** Bug 23508 has been marked as a duplicate of this bug. *** This is proving to be needed now more than ever. With libraries adjusting their circulation and fines rules to accommodate quarantines, closures, etc, it is particularly challenging to reset the rules "back to the way they were" when there is no way for the library to know what they were originally. This would be really helpful to our library. In addition to adding logs for circ/fine rules it would be helpful to be able to access those logs right from the specific rule on the smart-rules.pl page. Maybe add a 'logs' or 'history' button to the actions column. It would be definitely a useful tool. For example, we had a situation lately caused by a missing value in the «Fine charging interval» field within a rule. As a result, no late fines were charged for a specific patron category and item type. Having circulation rule modifications logs would have helped to identify when the issue started. +1 +1 The more complicated a library's configuration of Koha becomes, the more this issue is critical for troubleshooting, especially for consortia and parent/child item types. ++1 :-) +1 +1 |