http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=2660 ------- Comment #3 from rch@liblime.com 2008-10-16 23:11 ------- Submitted new patch allowing either of two behaviors: * default mode : when overdue_notices.pl runs, a notice is generated for each patron with an overdue item in one of the three defined notice periods. Up to three notices may be generated per patron. Example use : conditions: delay1 = 10 days delay2 = 20 days delay3 = 40 days cron script scheduled to run at 10 day intervals results: The patron will receive notice 1 sometime between 10 and 19 days after her item becomes overdue, depending on how the due date aligns with the cron schedule (for purposes of this example, let's assume the due date is off the cron schedule by 3 days, so the first notice is sent 13 days after the due date). The patron receives two copies of notice 2, since the cron script will run twice in the period between delay2 and delay3, at 23 days and 33 days. At 43 days, she receives her first copy of notice 3, and receives another copy every ten days thereafter until MAX (defaults to 90). Proper alignment of cron scheduling with delay settings can generate only one notice per period. The second mode of operation is triggered mode. This option is intended for a system running the cron script nightly, and so only generates a notice on those days when an overdue item reaches one of the delay triggers. This option removes the need to sync cron and delays, but carries a greater risk of missing notices. If the server fails in default mode, you can probably just run the script the next day without missing notices. In triggered mode, if the script fails to run, the notices that would have been generated will never be generated. In this mode, a patron should never receive more than three notices per item. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.