4104c69757
This commit adds two options to the overdue_notices.pl script. The notices are now generated in one of two modes: default or triggered. In default mode, every time the script runs, a notice is generated if an item is overdue within a notice date range. This mode is suitable for a weekly cron (or manual run), but the notice triggers should be syncronized with the cron script such that the script is run once per notice date range. Otherwise, duplicate messages will be generated ( or no notice generated if a notice date range passes without the script being run). Triggered mode is suitable for a nightly cron job: a notice is generated only on those days that an overdue item enters a notice date range. This mode is susceptible to message loss when the cron script fails to run, or when notice triggers are edited. A second flag is added: --list-all, which causes items.content to list all currently overdue items. Without this flag, only items that are overdue within the given notice's date range are listed on that notice. Signed-off-by: Galen Charlton <galen.charlton@liblime.com> |
||
---|---|---|
.. | ||
holds | ||
stats | ||
advance_notices.pl | ||
backup.sh | ||
build_browser_and_cloud.pl | ||
create_koc_db.pl | ||
crontab.example | ||
fines.pl | ||
j2a.pl | ||
longoverdue.pl | ||
notifyMailsOp.pl | ||
overdue_notices.pl | ||
process_message_queue.pl | ||
reservefix.pl | ||
services_throttle.pl | ||
smsoverdues.pl | ||
update_items.pl | ||
zebraqueue_start.pl |