SMS Messaging in Aleph 500 Version 20 and up Yoel Kortick

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Introduction The information contained here may also partially be found in the “Aleph 20 Syslib Guide – Circulation”. SMS Messaging in Aleph 500. Yoel Kortick, 2010

Cases where an SMS may be sent There are three specific cases in which Aleph 500 may be configured to send SMS messages to library patrons: Patron hold request is fulfilled Overdue letter is sent to patron An item that is on loan to a patron is recalled In this presentation we will use an example with the recall functionality. SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Proxy configuration Sending SMS messages depends on configuring and activating the SMS Server. The SMS Proxy documentation with information on the required configurations for the SMS Server may be found on the Doc Portal under: Cross Product Information > SMS Proxy SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Conditions Conditions by which the relevant printout will be sent by SMS The patron has a valid SMS number in his patron card. The SMS number may be input using the Address Information form of the Circulation GUI or using the Patron Registration and Address Information forms in the Web OPAC. The patron has agreed to receive SMS messages. The patron agreement is registered in the Global Patron Information and Patron Registration forms of the Circulation GUI, or in the Patron Registration and Address Information forms in the Web OPAC. The library has configured the form to trigger an SMS message (described further on here) SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 SMS Configuration #1 The first step is to define the sms_server in the $alephe_root/aleph_start file. For example: setenv server_sms "10.1.235.14:1894" SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 SMS Configuration #2 The second step is to define the $data_tab/form_sms table in the ADM library. This table is used to set which forms will trigger SMS sending. The following forms may be sent via SMS: hold-request-letter-xx. The xx is the hold request send action loan-recall-x. The x is the recall letter type (1 or 2) overdue-letter-x. The x is the optional letter number overdue-summary-x . The x is the optional letter number overdue-sum-single-x. The x is the optional letter number SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 SMS Configuration #2 $data_tab/form_sms table in the ADM library. The table includes the following columns: Column 1 – Name of the form Column 2 – The form number Column 3 – The SMS text number. This number must be aligned with the codes used in the $aleph_root/error_lng/sms_messages table, as described below. Column 4 – Whether or not the SMS message will be sent SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 SMS Configuration #3 In the $aleph_root/error_lng directory, the sms_messages table includes the SMS messages text. Column 1 of this table is the message text, and must be aligned with the code that is used in column 3 of the $data_tab/form_sms table. SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 SMS Configuration #4 If fee charging is required, tab18.lng must be set with the relevant charge. The SMS charge is 0072. SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (standard recall setup) We will use an example where an SMS message is sent when an item is recalled. In tab15.eng item status 07 is defined as recallable: 15A 07 ## L Seven Days Y Y Y Y Y N N Y Y 00 N A We will use an example where an SMS message is sent when an item is recalled. In tab16 item status 07 is defined as being due one day from the time cir-13 (recall) is run, and has a minimum loan period of 1 day: 16A 07 ## ## + 00000007 00 A 2200 0000 00300 020 010 4 001 001 M004 0009999.00 000 2 SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (standard recall setup) In tab100 the RECALL-METHOD is defined as 1 RECALL-METHOD=1 In tab18.eng the SMS charge is defined as 5 (units of currency) in the YOELK sub library. 0072 YOELK 07 ## Y 5.00 SMS Message SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Example (SMS setup) In USM50 $data_tab/form_sms we state that letters the loan-recall-1 and loan-recall-2 will be sent by SMS and will use message number 1207 from $aleph_error_eng/sms_messages Here is $data_tab/form_sms !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!-!!!!-! loan-recall-2 1207 Y loan-recall-1 1207 Y Here is $aleph_error_eng/sms_messages 1207 0000 L The following $2 items have been recalled in library $1: $3 due date is $4 SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Example (SMS setup) Third party SMS servers may be used for the actual SMS sending. If the files: $data_tab/form_sms and $aleph_root/error_lng/sms_messages are set up as explained then a <sms-message> tag will be created in the printout XML file. This text, along with the <z302-want-sms> and <z302-sms-number> tags information, may be used to activate third party SMS servers for the purpose of sending SMS messages. SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Example (SMS setup) The patron has an SMS number defined in his address: SMS Messaging in Aleph 500. Yoel Kortick, 2010

SMS Messaging in Aleph 500. Yoel Kortick, 2010 Example (SMS setup) The patron has “Receive SMS” checked in his global patron record: SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (recall workflow) Item barcode 65267-10 is item status 07 in sub-library YOELK. It uses tab15 and tab16 identifier 15A and 16A. It is on loan to patron 313972002 for 7 days (until June 8th) SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (recall workflow) The item is requested by patron 313972001 SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (SMS and recall workflow) The service “Recall items on loan (cir-13)” is run. The SMS is sent when the service completes, and not when the letters are printed. In this respect it differs from when emails are sent. SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (recall workflow) The due date has changed in accordance with tab16 definitions and the running of cir-13 It used to be 08/06/2010 SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (SMS and recall workflow) The output file is created. SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (SMS workflow) The letter is “loan-recall-1”. This letter was defined previously is $data_tab/form_sms. SMS Messaging in Aleph 500. Yoel Kortick, 2010

Example (SMS workflow) If the sms_server defined in aleph_start is an active 3rd party sms server then the following <sms-message> would have been sent to the following <z302-sms-number> because of the <z302-want-sms> field. This sms message would be sent when the letter is printed via “normal printing” USM50> grep sms $data_print/yoel_cir_13 <z302-want-sms>Y</z302-want-sms> <z302-sms-number>0547804062</z302-sms-number> <sms-message>The following 1 items have been recalled in library The Yoel Library: Kortick, Yoel 1971-: due date is 02/06/2010</sms-message> SMS Messaging in Aleph 500. Yoel Kortick, 2010

Yoel.Kortick@exlibrisgroup.com