Bug 24628 - Fine grained control over hold/auto-renew notice recipients
Summary: Fine grained control over hold/auto-renew notice recipients
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-11 08:12 UTC by Martin Renvoize
Modified: 2024-01-06 11:17 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 Martin Renvoize 2020-02-11 08:12:19 UTC
In bug 17014 comment 32 Ray requested a more advanced configurability of reserve notices as quoted below:

>No Notice Before parameter: Rather than this being a system preference I see it better as an additional column in the Circulation & Fine rules. This would be configurable line by line (user category / item type) and allow the Koha library to email as many or as few current holders of the non-renewed items as they wished.  Libraries that wanted to be more lenient that us could increase the No Renewal Before to 1, 2, or 3, say, but it would be the wise choice of a No Notice Before value that would be the best driver in targeting users whose items are likely to fulfil the reservation / hold.

> We have multiple copies of the same item (with various loan periods) out on loan. If a reservation is placed we want to send renewal-failure notification only to users whose copy is due “soon”, and not to people who have, say, just taken a long-term loan copy out. Native Koha auto-renewal functionality currently sees every holder of the item emailed.  But the first copy returned satisfies the reservation. Why pester everyone- we want to better target the email.
Comment 1 Katrin Fischer 2024-01-06 11:17:40 UTC
It feels like this should be 2 bug reports perhaps?