Bug 16201 - Tie automatic cancellation of expired holds to a system preference
Summary: Tie automatic cancellation of expired holds to a system preference
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-05 09:50 UTC by Katrin Fischer
Modified: 2023-09-09 19:12 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Katrin Fischer 2016-04-05 09:50:00 UTC
Currently, if you run multiple instances on a server, you can not easily configure for some, but not others, that holds not picked up will automatically cancelled. 

The cronjob used is:
misc/cronjobs/holds/cancel_expired_holds.pl

If it's scheduled, the feature is active for all instances - or you'd have to maintain a list, change the default cron files etc.

It would be nice if this feature was tied to a new system preference, so that you can easily activate/deactivate it from within Koha and without accessing the server.

This might also be useful for libraries that want to wait a little longer with cancelling in some cases, for example after a holiday period or when the library has been closed for a while.
Comment 1 Katrin Fischer 2023-09-09 19:12:57 UTC
This would still be nice to have :)