►Alerting> Notices
OLIB has a number of Alerting notices that can send an alert email when specific circulation transactions occur. For example you may want to configure a notice that sends an email to a User when they make a renewal through the OPAC - as a type of confirmation. In practice you can configure a notice for any other circulation transactions too, these include:
Transactions: Issue - Collect - Issue on permanent loan - Collect on permanent loan - Renewal - Unseen Renewal - Automatic Renewal - Return - Claims Lost Return - Non-loan Return (sent to a To List not a 'borrower') - Issued In Transit (should be sent to a To List not a 'borrower') - Returned In Transit (should be sent to a To List not a 'borrower')
In Alerting> Notices, you can select these circulation transaction types from the Circulation Transaction drop down in the circulation Notice Details.
Other circulation transaction types either already have alert types (Res. Held Notification, etc.) or are not suitable for alerting. The Notices domain includes an Example Notice for each circulation transaction type. You can make a copy of these, specific to your organisation and configure them e.g. by adding From Address and Enabled=Yes. The circulation transaction that triggers the alert email is displayed at the foot of the notice.
You can configure more than one alert for a transaction type. They can be different based on the Locations, User Categories and Copy Categories that apply.
Caution: it is normally preferable to configure your own copy of an alert so that it cannot be overwritten by a subsequent OLIB upgrade.
<CT_ID> | copytrans record number |
<CT_CTRANTP> | circulation transaction type key ID |
<CT_CTRANTPLD> | circulation transaction type long description |
<CT_CTRANTPSD> | circulation transaction type short description |
<CT_PROCDATE> | copytrans processed date |
<CT_TRANDATE> | copytrans transaction date |
<CT_TRANS_USER> | the name of the user who performed the transaction |
<CT_ADDRESS> | issue address (used for postal loan confirmation alerts) |
<CT_TRANS_SOURCE> | the transaction source (WorldView, OLIB Web, etc.) |
<CT_MANTRAN_DATE> | copytrans manual transaction dat |
Here is the text from the Example Renewal record:
<body><basefont size="3" color="blue" face="Arial"/>The following renewal transaction has been recorded:<BR><BR>Transaction ID: <CT_ID><BR>Borrower: <CT_TRANS_USER><BR><BR>Title: <TI><BR>Copy: <CP_BC><BR><BR>Renewed on: <CT_TRANDATE><BR>Due back on: <CP_RETDATE></body>
To List: used to specify who the notice should be sent to if it is not to be sent to the user.
CC List: enter an email address to which a copy of the notice should be sent.
BCC List: enter an email address to which a blind copy of the notice should be sent.
Tip: in all three of the above fields, multiple email addresses can be entered. Multiple addresses should be separated with a semi-colon.
When a circulation transaction alert is sent to a user, the details of this can be viewed in Users: Email Notice History as described in View User Details.