These are required by the Circulation module if the automated overdue system is to be implemented. The example notices here provide the text of each individual overdue notice, for example, a first, second and final overdue notice. Recall notices are also created here. Overdue and Recall messages can also be sent via SMS Texting.
Notices can be used to:
- configure the content and format of the overdue notice
- determine who the notice should be sent to
- whether it should be CC'd and/or BCC'd and the subject line of the email
For emails, the text uses the same syntax as used for configurable export formats: the OLSTF format.
The Location, User Category and Copy Category are not used in Overdue Notices because these values are taken from Loan Terms. (The Overdue Notice is attached to an Overdue Sequence and this is attached to Loan Terms). Users and Media Type(s) are also not used for Overdue Notices.
Create overdue notice
Caution: copy the text from the Example First Overdue Notice into a new Notice that you create. Do not configure any Example notices and run them, as these would be overwritten with a new copy of the Example when a future OLIB upgrade is applied.
- A wildcard (%) search in this domain shows the Example First Overdue Notice already provided with OLIB.
- Select this record and in Other Actions choose Create Close Copy.
- Click on the copy to display full details and modify record:
|Notice No.||System generated unique number.|
|Notice Type||Set to Overdue Notice.|
|Brief / Full Description||Enter to identify this notice|
Change the contents to specify the text and punctuation you wish to include in the email to the users. This is using the same syntax as is used for configurable export formats to define the main body of the email. The OLSTF Tags table indicates which User and Copy tags are available for you to use in the Notice Text field for overdue notices. For example, to include data from a field in the user record, enter the User OLSTF tag surrounded by angle brackets. If you only want the text to be included if the field itself contains data, surround the OLSTF tag and associated text with the appropriate hash tag combination:
<body><basefont size="3" color="blue" face="Arial"/>Dear <TIU> <SN>,<br /><br />According to our records, the items listed below which are currently on loan to you are overdue. Please either renew them or return them to the library immediately. Fines are accruing on them on a daily basis, so the longer you leave it the more you will have to pay.<br /><br />Yours sincerely,<br />Insert Name Here<br />Insert Position Here<br />Insert Library Name Here<br /><br /><TABLE WIDTH="650"><TR><TD WIDTH="100"><B>Barcode</B></TD><TD WIDTH="350"><B>Title</B></TD><TD WIDTH="100"><B>Due Back</B></TD><TD WIDTH="100"><B>Current Fine</B></TD></TR>#ITEM#<TR><TD VALIGN="TOP"><BC></TD><TD VALIGN="TOP"><COTI></TD><TD VALIGN="TOP"><RETDATE></TD><TD VALIGN="TOP"><CF></TD></TR>#/ITEM#</TABLE></body>
Remember to also complete librarian's name and position, and location name where indicated. The example above contains HTML tags so that the email is properly formatted and reads as follows:
Set to To user's email address for the notice to go to the email address in the User's record.
Note: the Users Email ID field is used, not the email field in the Address details.
If the User's email address is missing, OLIB sends the Notice to the email address you enter in the To List field. This means you can send overdue notices to yourself, for Users who do not have an email address; they can be printed and posted off to the user.
If you set Transmit Type to To To List the Notices are sent directly to the email address in the To List field. This can be used if you want notices to always go to a member of staff, e.g. for printing and posting, rather than directly to the Users.
Alternatively, you can set the Transmit Type to To user's supervisor for the notice to go to the Supervisor rather than the user who has the items. This can be used perhaps for a final overdue that you may wish to send to a Supervisor or Tutor.
If you set Transmit Type to To Copy’s Location, the notice is sent to the Location’s email address, for example for shelf checking and annotation with the replacement cost, before sending the letter to the user.
|Send single email||Only set to Yes if sending a single email attachment for multiple overdues.|
|CC To Supervisor||Yes/No whether notice is copied to student supervisor entered on the user's record.|
|From Address||Enter a valid email address, e.g. a generic address for your library, so that, if the User clicks the Reply button, the reply email will be delivered to the appropriate member of staff who deals with User responses to overdue notices.|
Configure the recipients of the email:
To List: used to specify who the loan reminder notice should be sent to if it is not to be sent to the user.
Tip: in all three of the above fields, multiple email addresses can be entered. Separate multiple addresses with a semi-colon.
Enter the text to be used as the subject line of the Overdue Notice.
|Enabled||Set to Yes.|
|SMS Notice Text||If this alert is to be sent as a text message instead of, or as well as an email, enter the text.|
|SMS or Email?||Select from the drop down SMS, Email or Both.|
As shown above, the notice will automatically contain location address, name and address of user, details of overdue items, and if appropriate, fines.
When each Notice is configured, e.g. First, Second, Third Overdue Notice, compile these into Overdue Notice Sequences.
Send overdue notices as an attachment
From OLIB 9 SP14 onwards, if you have still not implemented this aspect of overdue notices and would like to, please contact your local OCLC Support office to discuss alternative options.
An overdue letter can be generated from an RTF template attached to the notice record and sent as an attachment to the email. In this way, graphics such as the library’s logo, can be included in overdue letters. The RTF template will be a standard document with your library’s logo, address, letter text, etc., together with an <ITEMS> tag in the relevant point in the letter, saved as an rtf file. The <ITEMS> tag will be replaced by the details of the overdue items, as defined in the relevant output format record. A model RTF template can be downloaded from the OLIB For Customers web site. Note that if you use the overdue/recall address flag in Users addresses, the rtf file needs to include the UOR tags listed above in Notice Text.
For help in editing the rtf, see Edit rtf notices.
Caution: it is recommended you do not use MS Word to edit overdue RTF templates.
The following configuration is required to set OLIB to send an overdue notice as a letter attached to an email rather than as an email:
- A copies Output Format record for use in overdue notices is delivered as standard, you may wish to review this first. (It is linked to the Example First Overdue Notice notice OP003 and may be linked to any notices you have configured). Alternatively create a new Output Format record. From the Menu, select Data Exchange Reference Data> Output Formats.
- Complete the Description field. For example, enter a description such as Format for the copy details of the overdue notice rtf file. Ensure that the Domain field is set to Copies.
- Enter the output of the notice in the Format Text field.
A typical output format record would contain the following in the Format Text field:
<CP_BC> - <CP_COTI>\tab <CP_RETDATE>\tab <CP_CF> \tab <CP_CP>
The '\tab' and '\par' parts of this text are rtf codes for the TAB character and the 'new paragraph' marker. The above format will display the copy barcode and title (separated by space-hyphen-space), then a tab, then the return date, then another tab, and finally the current fine. A carriage return will then be added so that the next copy is displayed on a new line.
Titles OLSTF tags can also be included, e.g. <ST>.
Other items user has on loan: you can also include details of other items the user has on loan. Use the <OITEMS> tag, e.g.:
The following is a list of the other items that are currently on loan to you. Please note that some of these may also be overdue, but not sufficiently as to have generated an overdue notice for them:
- Set up the Overdue Notices and link them to the Overdue Sequences and Loan terms as described in Overdues configuration.
- On the Overdue Notice record attach an RTF template as described above, in the Object field.
- Set the Object Type to ASCII text. Ensure that the In Database and Import Now flags are set to Yes before saving the object, so that the rtf template is imported into the database.
- Set the notice record's Incl. As Attachment? field to Yes.
- Set the notice record's Output Format to the correct Output format, e.g. Format for the copy details of the overdue notice rtf file. The format for use in overdue notices is delivered as standard. It is linked to the Example First Overdue Notice notice OP003 and may be linked to any notices you have configured.
The overdue letter will be included as an attachment to the email that is sent to the user, To List email address(es) and/or the user’s supervisor.
The library can also receive a single email that includes a single attachment containing all the overdues.
Alternatively, Overdue letters can be printed rather than sending them as attachments to an email.
- Configure the overdue notice as described above.
- Set the notice record’s Transmit Type to To To List.
- Enter the email address of an email account which a mail-to-print gateway is monitoring.
The mail-to-print gateway will pick up the email and print the attached letter to the designated printer. These letters can then be collected for sending to the user and/or the user’s supervisor.
Copy/User Location-specific letters
To use this feature, the system manager first needs to add the Copy/User Location Letter field to your Overdue notice layout using Layout Manager.
It is possible to link several letter RTF templates to an overdue notice record, one for each location to which the overdue notice is sent. In this way, a different letter can be generated and sent which is specific to the location to which it is being sent.
Location-specific letters are entered in the new Copy/User Location Letters field using the following workflow:
- With the notice record in modify mode, click New under the Copy/User Location Letters field ;
- Enter the details of the location’s letter RTF template as usual. (Don’t forget to set In Database and Import Now to Yes before saving the new object) ;
- On return to the notice screen, select the letter you just added and select the Set/Clear location action ;
- This displays a pop-up window with the list of locations. Select the location whose letter you’ve just added and click OK to return to the notice record ;
- The location should now be displayed to the left of the hyphen ;
- Repeat for the other locations’ letters.
Note that you will not be able to add another copy/user location letter until you have set the location for all existing copy/user location letters using the above workflow.