https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19260
Bug ID: 19260
Summary: Reservations / holds marked as problems being seen as
expired ones and deleted wrongly.
Change sponsored?: ---
Product: Koha
Version: 17.05
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Hold requests
Assignee: koha-bugs@lists.koha-community.org
Reporter: r.delahu...@arts.ac.uk
QA Contact: testo...@bugs.koha-community.org
CC: gmcha...@gmail.com
We have the ReservesMaxPickupDelay set to 7 and the
ExpireReservesMaxPickupDelay system parameter set to Don’t Allow.
Our workflow is that staff use the report generated by waitingreserves.pl to
identify titles to retrieve from the Reservations / holds awaiting pickup
shelf, and delete the reservation and return the items to the shelf, or have
that action trigger reservation satisfaction for the next person in the queue.
Since our upgrade for 16.05 to 17.05 we are finding that when we run the
cancel_expired_holds.pl job at 01:00 daily, reservations marked as problem ones
are being deleted in addition to expired ones (expiration date set by user has
been reached, or the default 100 days has been reached). Koha 17.05 appears to
be disregarding the ExpireReservesMaxPickupDelay system parameter.
(http://translate.koha-community.org/manual/master/en/html/17_cron_jobs.html#expiredholdscron).
We have suspended this cron job in the meantime, and will write a query to
identify expired ones we need to delete. Ideally we want problem reservations
NOT to be seen as expired ones.
Ray Delahunty
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
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/
