[Bug 33096] New: DefaultHoldExpirationdate does not show date when placing hold
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33096 Bug ID: 33096 Summary: DefaultHoldExpirationdate does not show date when placing hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 The preference DefaultHoldExpirationdate, when set, doesn't show the date in the expiration field while placing the hold, in either the staff side or the opac side. So you don't know there is a default until after the hold is placed. This is extremely counter productive, because you can't change the expiration date on a hold. You then have to cancel the hold, and replace it and put the date you want in place. This should be fixed. -- 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=33096 Emmi Takkinen <emmi.takkinen@koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emmi.takkinen@koha-suomi.fi -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33096 --- Comment #1 from Emmi Takkinen <emmi.takkinen@koha-suomi.fi> --- (In reply to Christopher Brannon from comment #0)
The preference DefaultHoldExpirationdate, when set, doesn't show the date in the expiration field while placing the hold, in either the staff side or the opac side. So you don't know there is a default until after the hold is placed.
This is extremely counter productive, because you can't change the expiration date on a hold. You then have to cancel the hold, and replace it and put the date you want in place.
I assume you mean that expiration date can't be changed in OPAC? Because changing it from the staff side seems to be working fine. So from OPAC point of view this sure isn't ideal situation. To fix this we could: 1) show default expiration date to the field while placing hold 2) allow patrons to change expiration date via OPAC (this should probably be a syspref) 3) do both. -- 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=33096 --- Comment #2 from Christopher Brannon <cbrannon@cdalibrary.org> --- (In reply to Emmi Takkinen from comment #1)
I assume you mean that expiration date can't be changed in OPAC? Because changing it from the staff side seems to be working fine.
Yes, thank you for the clarification.
So from OPAC point of view this sure isn't ideal situation. To fix this we could: 1) show default expiration date to the field while placing hold 2) allow patrons to change expiration date via OPAC (this should probably be a syspref) 3) do both.
Both would be preferable, but at least option 1. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org