https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29003
Bug ID: 29003
Summary: Apply different reasons via cancel_expired_holds cron
based on found value
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Circulation
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected], [email protected]
Depends on: 12656
Bug 12656 allows one to define a cancellation reason when running the
cancel_expired_holds cron. That reason is recorded for later reporting and also
triggers a notice.
That cron cancels both holds that have simply never had an item captured *and*
holds where the item has been waiting on the hold shelf past the pickup delay.
Ideally, we'd be able to tell the cron to apply two different reasons in these
two very distinct cases.
Maybe the cron could take a pair of [found value]=[reason]? So you could set it
with something like:
'W'='TOO_LONG'
NULL='UNFILLED'
Referenced Bugs:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12656
[Bug 12656] Allow a CANCELLATION_REASON to be specified on the
cancel_expired_holds.pl job
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://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/
