Lines 51-58
overdue_notices.pl - prepare messages to be sent to patrons for overdue items
Link Here
|
51 |
overdue_notices.pl |
51 |
overdue_notices.pl |
52 |
[ -n ][ -library <branchcode> ][ -library <branchcode> ... ] |
52 |
[ -n ][ -library <branchcode> ][ -library <branchcode> ... ] |
53 |
[ -max <number of days> ][ -csv [<filename>] ][ -itemscontent <field list> ] |
53 |
[ -max <number of days> ][ -csv [<filename>] ][ -itemscontent <field list> ] |
54 |
[ -email <email_type> ... ] |
54 |
[ -t|-triggered ][ -list-all ][ -date ][ -email <email_type> ... ][ -v ] |
55 |
|
55 |
|
56 |
Options: |
56 |
Options: |
57 |
-help brief help message |
57 |
-help brief help message |
58 |
-man full documentation |
58 |
-man full documentation |
Lines 64-71
overdue_notices.pl
Link Here
|
64 |
-itemscontent <list of fields> item information in templates |
64 |
-itemscontent <list of fields> item information in templates |
65 |
-borcat <categorycode> category code that must be included |
65 |
-borcat <categorycode> category code that must be included |
66 |
-borcatout <categorycode> category code that must be excluded |
66 |
-borcatout <categorycode> category code that must be excluded |
|
|
67 |
-list-all include all overdue items in the list (limited by <-max> setting) |
68 |
-triggered|t generate a notice if and only if an item is overdue by the number of days defined in a notice trigger |
69 |
-date send overdues on a specific date and not Now |
67 |
-email <email_type> type of email that will be used. Can be 'email', 'emailpro' or 'B_email'. Repeatable. |
70 |
-email <email_type> type of email that will be used. Can be 'email', 'emailpro' or 'B_email'. Repeatable. |
68 |
|
71 |
-v verbose mode |
|
|
72 |
|
69 |
=head1 OPTIONS |
73 |
=head1 OPTIONS |
70 |
|
74 |
|
71 |
=over 8 |
75 |
=over 8 |
72 |
- |
|
|