http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7408
--- Comment #2 from Ian Walls <[email protected]> 2012-01-05 23:42:53 UTC --- Nicole, No, cancel_expired_holds.pl moves holds from being expired to being cancelled, and thus moved to the old_reserves table. Not every waiting hold has an expiration date; it's not filled in by the holds fill process. The patron or librarian has to set it manually. What's needed is an automated way of adding these expiration dates based on the ReservesMaxPickupDelay value, so that cancel_expired_holds.pl can capture and cancel them. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- 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/
