https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22573 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- If it has already an expiration date that would have been set by the patron when starting the hold 'not needed after...'. So actually the patron indicated they no longer need it... I wonder if those shoudl not be set to waiting but move on to the next patron immediately? -- 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=22573 e.betemps <e.betemps@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |e.betemps@gmail.com -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22573 Juliet Heltibridle <jheltibridle@rcplib.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jheltibridle@rcplib.org --- Comment #3 from Juliet Heltibridle <jheltibridle@rcplib.org> --- Our holds are canceled by a cron if the expiration date is in the past, so this problem does not affect us in that way. But if a patron has chosen to set a "not needed after.." date, they often mean that they don't want it if it hasn't been placed on the hold shelf by that date, but they still want the 7 days to pick it up if it has been moved to waiting by that date. So we are seeing holds that are scanned in at our library and have an expiration date that is shorter than the 7 days we have set for our ReservesMaxPickUpDelay. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.