[Bug 13756] New: Holds over date
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13756 Bug ID: 13756 Summary: Holds over date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com Would like to see hold over date calculated at time of hold and recorded in the requests table with the hold. As I understand it, holds over dates are calculated when the holds over table is looked at. This is a very loose calculation, since if the value of ReservesMaxPickUpDelay is changed at any time, the holds over period changes with that, regardless of when the hold was filled. Some libraries may prefer to have that date fixed in place on the table, while others might want the fluid, on the spot calculation, so perhaps it should be an option. For me, as someone dealing with consistency and reports, a fixed date in the table is preferred. It would be great to be able to run custom reports and see those dates. It would be great to have that date show in the holds information for both item and patron screens on the staff side. It would be great to be able to print that date on the hold slips. It would be great to know that if we let patrons know how long they have to pick something up, that won't change because an adjustment is made to ReservesMaxPickUpDelay (although, how often does that happen?). My two cents. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13756 Tom Misilo <misilot@fit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |misilot@fit.edu -- You are receiving this mail because: You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13756 --- Comment #1 from Christopher Brannon <cbrannon@cdalibrary.org> --- Another benefit of going this route is that it will lend itself to more flexibility down the road, if for example, the holds over date (the ReservesMaxPickUpDelay which should be renamed to HoldsOver) is set for each library in the circulation rules rather than a global setting. This one is my 3 cents, making an even nickel. :) Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org