[Koha-bugs] [Bug 7408] Expire holds that have been waiting too long
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Feb 7 20:22:30 CET 2012
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7408
--- Comment #4 from Owen Leonard <oleonard at myacpl.org> 2012-02-07 19:22:30 UTC ---
I've tested this successfully but have one question about how it works: After
running the script, the holds get an expiration date of today. Running
cronjobs/holds/cancel_expired_holds.pl immediately afterwards will cancel
expired holds, but only those with an expiration date *less* than today. So
none of the holds expired by this new script will be cancelled. If I then run
the new script again with the --charge option the user will get double fines.
I know this isn't they way the script would typically be run, but it's
worrisome to me.
On another note, testing this makes me wonder: Why don't we simply set an
expiration date at the time the hold is marked waiting, based on the
ReservesMaxPickupDelay setting?
--
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the Koha-bugs
mailing list