https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33552
--- Comment #4 from Ray Delahunty <[email protected]> --- Auto-renewal logic has changed a lot but there still are many challenges. Yes, ‘pointless emails’ are a problem (bug 35656 doesn’t help!). But we want the opposite of what is suggested here. Our patrons are told the items will renew 9 times (for ten 1 week loan periods) and we want to email them only if that routine is stopped. Ideally the development direction auto-renewals takes generally will offer choice, so the customer can select preferred functionality. Koha administrators have subtly different expectations for how auto-renewal should work. The functionality is puzzling at times, for example with potentially duplicate emails from different notices (see bug 38203). And our 23.11 still sends digests for the too_many error as well as the auto_renewal_final one but we are delighted it does despite what bug 34924 says. Yes, we have multiple too_many (and other DGST emails duplicated) but that is down to bug 35656. In the absence of a product manager who defines the LMS roadmap, getting agreement as to what should be ‘standard auto-renewals functionality’ is always going to be a challenge that open-source Koha faces. -- 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/
