https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24203
--- Comment #4 from Katrin Fischer <[email protected]> --- (In reply to Christopher Brannon from comment #3) > (In reply to Katrin Fischer from comment #2) > > Can you explain this with an example maybe? > > Itemtype A could go long overdue after 28 days. > Itemtype B could go long overdue after 14 days. > Itemtype C could go long overdue after 7 days. > > How can you set overdue notices to coincide with those overdue times? You > can't. Right now, to cover everything, you would have to set the trigger > time to be 28 days to accurately cover everything. Except there would be a > delay on the notices for the itemtypes that go overdue 7 or 14 days. Hi Christopher, we don't use the longoverdue process ourselves, I was not aware that it's used in combination with the overdue notices. This is really interesting. For our libraries the major concern is that it should be timed with the creating of fines, which is usually happening in a weekly interval here. I wonder if it could make sense to not tie it overdue notices but to their own set of notices by itemtype? Both could live on the same configuration page tho. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ 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/
