►System Administration> Server Process Config
►System Administration> OLIB Defaults
This information explains how to set up email alerts and SMS (text) alerts, including Janet txt.
If email alerting is to be used, go to System Administration> Server Process Configuration and enter your SMTP server name.
Text alerts can be used for Overdues, Recalls, Reservation Held Notifications, Loans Due Reminders.
Enter SMS configuration details. These can be set at the users' Location level and/or system level in OLIB Defaults. If details are not entered at Location level, OLIB uses the details at System level.
- In both cases go to the SMS Alerting Configuration sheet.
- In modify mode, complete the following fields and save the details:
|Aggregator||The aggregator to use, e.g. Blackboard ConnextTxt, Janet txt, firetext.|
|Certificate Store||Enter the location of the Oracle certification wallet (supplied by OCLC’s OLIB Technical Services department). Edit the certificate authority for the aggregator you want to use. For example for firetext this will need to include COMODO root certificates. This may be carried out as part of a Service Pack upgrade, or OCLC may need to liaise with your DBAs in order to implement the updated Certificate Store.|
|URL||The aggregator’s URL: e.g. the Janet txt gateway (supplied by Janet txt), or e.g . https://www.firetext.co.uk/api/sendsms|
|Account User Name / Password||The email address and password of your account with the aggregator to log into the account online.|
|Alerts Sent From||The 'from address' that will be included in the SMS messages - i.e. a short piece of text to inform your users that the message is from your library (letters/numbers only and between 3 and 11 characters).|
|Suppress Unicode?||Set to Yes|
|Reporting Level||The diagnostic level that you want to operate. Normally set to NONE.|
|Retrieve Statuses?||Normally set to No. (The OLIB SMS Service can send status update requests to the aggregator to monitor the progress of the SMS messages it has requested to be sent).|
|Start Time||The earliest time that you would like OLIB to send SMS messages. The SMS messages are actually generated in daystart. However, you may not want OLIB to send SMS messages to your users as early as this. You can therefore set Start Time to a 'reasonable' time such as 08:00 so that the texts are actually sent 'during normal office hours'.|
|End Time||Similarly, you may not wish your OLIB system to send texts beyond a certain time of day.|
|Proxy Server||Add the proxy server details if you have to use a proxy server.|
|Proxy User Name|
|User Agent||Set to Use default location for UserAgent. Other options will be implemented in a future release.|
- After completing the above details click Save and Continue (if you wish to run a test) or Save.
- Test SMS: in the Locations and OLIB Defaults layouts the Test SMS button is standard. Click this button to send a test text message containing some standard text, to the relevant aggregator e.g. firetext. When successful, OLIB displays a popup similar to this:
Judith Seddon - SMS 670885
<?xml version="1.0" encoding="utf-8"?>
0:1 SMS successfully queued</SingleResponse>
A message is also directed to the mobile number present in your User record (i.e. whoever you are currently logged into OLIB Web as), e.g:
Judith Seddon – SMS 670885
This includes the name of the current user record and a random 6 digit number.
- In the Users domain, for each User record ensure you are entering the user's mobile telephone number in the Main Details:Tel. Mobile field. (If the user’s record does not contain a mobile number, the alert will be generated as normal, but it will be flagged as Not Sent).
In Notices create a copy of the example notice you want to send.
- Select the Notice Type.
- Edit the Notice Text. (Not required if the alert will only be via SMS).
- Set Enable to Yes and any other email settings etc..
- Enter the SMS Notice Text if this notice is to be via SMS.
- Specify whether the notice is to be sent via Email/SMS/Both.
Specify From Address and Reply To Address
This configuration is optional. It is possible to apply a global From address for all emails, and also to configure OLIB so that the email address that is entered in the From Address field in the notice record is put in alternative email headers such as On-Behalf-Of and Reply-To.
These are entered in Email System Settings in OLIB Defaults.
Go to > System Administration> OLIB Defaults > Reports / Email Configuration.
Enter a new global From address and additional Replacement Headers:
|From Address||The email address to use as the From address in all emails, in place of the From Address that is configured on, for example, the Notice record. When used, the From address that is configured on the Notice record is placed against each of the headers specified in the Replacement Headers field below.|
These are one or more headers you want included in the emails sent from your OLIB system. These are as well as the From header. These headers will then include the email address that exists in the originating notice's From Address.
This means for example, hosted systems can all have an oclc.org From Address (by dint of the system being implemented on the managed service) - but also a local library Reply-To, so recipients can actually reply to the email. For example, the Notice would contain:
From Address: “My Local Library” <NoReply@oclc.org>