Configuring the SMS overdue notification blocks

By default, the day end processing for SMS notification of overdue items is turned off.

This allows you to set all the settings and test the SMS feature before turning it on for day end processing.

The location for circ_privilege is based on the setting in the matham Mq view, in the Circ Settings by field. If the value is set to Item's Location, then max notices and notice delay should be the values from the item’s location. If the value in matham is set to Circ Location (checkout location), then use the checkout location for the values.

An SMS overdue block will be generated for every overdue (od block) if it is time to generate the overdue notices. However, you must account for the Notice Delay for overdue blocks (first notice delay plus notice interval in circ_privilege), because SMS overdue blocks will not be created if there is not enough time to generate them.

You can set up a notification block for one or more SMS overdue notices: First, second, third, and final. The configuration steps are the same for each one.

To configure the SMS hold notification block type

1 Open the block view in Table Editor.
2 Locate and select to edit the odsmsN (where N is 1, 2, 3, or F) block type.

Note: You can add additional block types if your library wants to configure more than 4 messages. For example, you could add odsms4 and odsms5.

3 Set the appropriate values for the fields. For more information about the fields, see Fields: Edit Block Types.

Default Language and the Notice Language group are the main fields that need to be set up for each SMS overdue notification block.

4 Click Save.

The SMS overdue notification settings will take effect after the next restart of Horizon and Horizon Information Portal. Any item that becomes overdue after this time will go through the SMS day end process for notifications. If Count SMS Overdue Notice as Sent was not selected in the sms_control view, the hnphone or hnmail block (or both) may be added to the borrower's burb record and a phone or mail notice (or both) may be generated by the Day End process.

However, the SMS overdue notification will not be sent if any of the following cases are true:

The Enable SMS Overdue Notice option is not selected in the sms_control table (for the system and for the borrower's location if there is an exception).
Borrower does not have any SMS opt-in phone numbers specified.
Borrower's specified SMS phone number is not associated with an sms_enabled phone type.
Borrower has not opted-in to receive overdue notifications to any specified SMS phone numbers.
The item is no longer overdue (it was checked in) at the time the message is prepared to be sent.
The Notice number in the burb is greater than the max notice value in circ_privilege. A lost block will then be generated.
The last notice block (noticeN) of the item is mail notices with a print flag of 1. No noticeN notices will be generated in this instance as well.
Borrower has a 'pcr' (Phone Correction Request) block in the burb table.
The SMS block in the burb has been sent (print_ notice flag is 1).

 

 


© 1998-2017 Sirsi Corporation