http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10744
Bug ID: 10744
Summary: ExpireReservesMaxPickUpDelay has minor workflow
conflicts with hold(s) over report
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Hold requests
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
Turning on ExpireReservesMaxPickUpDelay means that the hold(s) over part of the
holds awaiting pickup report (circ/waitingreserves.pl) can be confusing.
Specifically, if the hold cancellation cronjob runs before the library opens,
the hold(s) over list will never contain any contents -- all of the holds that
have hit the max pickup delay will have been cancelled.
Having a report that will never produce results can be (and has been for at
least one of our customers) confusing.
I can think of a couple options for improving this:
- suppress the display of the hold(s) over tab if ExpireReservesMaxPickUpDelay
is on.
- have the hold(s) over report display the list of waiting holds that were
canceled
- today or
- the last time cancel_expired_holds.pl was run
- as alternative or in conjunction with one of the other options, have
cancel_expired_holds.pl create a report of cancelled waiting holds to assist
with clearing the items from the holds shelf
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
