[OPEN-ILS-GENERAL] SMS Hold Notifications

[Morgan, Michele]

We are looking at making improvements to our SMS hold notification
template. Right now we're using the out of the box template in our trigger:

[%- USE date -%]
[%- user = target.0.usr -%]
From: [%- params.sender_email || default_sender %]
To: [%- params.recipient_email ||
helpers.get_sms_gateway_email(target.0.sms_carrier,target.0.sms_notify) %]
Subject: [% target.size %] hold(s) ready

[% FOR hold IN target %][%-
  bibxml = helpers.xml_doc( hold.current_copy.call_number.record.marc );
  title = "";
  FOR part IN bibxml.findnodes('//*[@tag="245"]/*[@code="a"]');
title = title _ part.textContent;
  END;
  author = bibxml.findnodes('//*[@tag="100"]/*[@code="a"]').textContent;
%]TITLE:[% title %] @ [% hold.pickup_lib.name %]
[% END %]

Which generates something like this:

From: evergr...@noblenet.org
To: 4135551...@vtext.com
Subject: 1 hold(s) ready

TITLE:Life, the universe and everything @ Danvers


One issue we are having is with replies to these messages. A patron may
reply asking to cancel the request, but there's no way to identify the hold
from their reply.

If you have made improvements to your SMS template, can you share what you
have done?

Thanks,
Michele
--
Michele M. Morgan, Technical Assistant
North of Boston Library Exchange, Danvers Massachusetts
mmor...@noblenet.org

Re: [OPEN-ILS-GENERAL] SMS Hold Notifications

[Thomas Berezansky]

I suppose I should add that, as far as I recall, MVLC also sends them  
out as a no-reply address. Largely due to the "can't get anything  
useful for information out of the reply" bit in our case.


Quoting Ben Shum :


For Bibliomation, we only added an event parameter for "sender_email"
to be "no-re...@biblio.org" for that action/trigger event definition.
With SMS text messages, there was no good way to give users a reply
location that would work consortium-wide.  So, while it's bad that we
do not give users any way to respond since no-reply is a dead-end, it
was assumed that patrons would find other means of contacting the
library (phone. email, etc.) if they needed to change the nature of
their hold request.  For a time, we thought about tacking on a "please
contact your library" statement to the messages, but that added too
much text to the text message itself, which ruins the whole point of
using short text messages with character limits.

I do not have any collected feedback from actual users on how they
perceive these actions on our part.

-- Ben

On Tue, Nov 3, 2015 at 10:09 AM, Morgan, Michele  
 wrote:

We are looking at making improvements to our SMS hold notification template.
Right now we're using the out of the box template in our trigger:

[%- USE date -%]
[%- user = target.0.usr -%]
From: [%- params.sender_email || default_sender %]
To: [%- params.recipient_email ||
helpers.get_sms_gateway_email(target.0.sms_carrier,target.0.sms_notify) %]
Subject: [% target.size %] hold(s) ready

[% FOR hold IN target %][%-
  bibxml = helpers.xml_doc( hold.current_copy.call_number.record.marc );
  title = "";
  FOR part IN bibxml.findnodes('//*[@tag="245"]/*[@code="a"]');
title = title _ part.textContent;
  END;
  author = bibxml.findnodes('//*[@tag="100"]/*[@code="a"]').textContent;
%]TITLE:[% title %] @ [% hold.pickup_lib.name %]
[% END %]

Which generates something like this:

From: evergr...@noblenet.org
To: 4135551...@vtext.com
Subject: 1 hold(s) ready

TITLE:Life, the universe and everything @ Danvers


One issue we are having is with replies to these messages. A patron may
reply asking to cancel the request, but there's no way to identify the hold
from their reply.

If you have made improvements to your SMS template, can you share what you
have done?

Thanks,
Michele
--
Michele M. Morgan, Technical Assistant
North of Boston Library Exchange, Danvers Massachusetts
mmor...@noblenet.org





--
Benjamin Shum
Evergreen Systems Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
203-577-4070, ext. 113



--
Thomas Berezansky
Assistant Network Administrator
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-8161

Re: [OPEN-ILS-GENERAL] SMS Hold Notifications

[Ben Shum]

For Bibliomation, we only added an event parameter for "sender_email"
to be "no-re...@biblio.org" for that action/trigger event definition.
With SMS text messages, there was no good way to give users a reply
location that would work consortium-wide.  So, while it's bad that we
do not give users any way to respond since no-reply is a dead-end, it
was assumed that patrons would find other means of contacting the
library (phone. email, etc.) if they needed to change the nature of
their hold request.  For a time, we thought about tacking on a "please
contact your library" statement to the messages, but that added too
much text to the text message itself, which ruins the whole point of
using short text messages with character limits.

I do not have any collected feedback from actual users on how they
perceive these actions on our part.

-- Ben

On Tue, Nov 3, 2015 at 10:09 AM, Morgan, Michele  wrote:
> We are looking at making improvements to our SMS hold notification template.
> Right now we're using the out of the box template in our trigger:
>
> [%- USE date -%]
> [%- user = target.0.usr -%]
> From: [%- params.sender_email || default_sender %]
> To: [%- params.recipient_email ||
> helpers.get_sms_gateway_email(target.0.sms_carrier,target.0.sms_notify) %]
> Subject: [% target.size %] hold(s) ready
>
> [% FOR hold IN target %][%-
>   bibxml = helpers.xml_doc( hold.current_copy.call_number.record.marc );
>   title = "";
>   FOR part IN bibxml.findnodes('//*[@tag="245"]/*[@code="a"]');
> title = title _ part.textContent;
>   END;
>   author = bibxml.findnodes('//*[@tag="100"]/*[@code="a"]').textContent;
> %]TITLE:[% title %] @ [% hold.pickup_lib.name %]
> [% END %]
>
> Which generates something like this:
>
> From: evergr...@noblenet.org
> To: 4135551...@vtext.com
> Subject: 1 hold(s) ready
>
> TITLE:Life, the universe and everything @ Danvers
>
>
> One issue we are having is with replies to these messages. A patron may
> reply asking to cancel the request, but there's no way to identify the hold
> from their reply.
>
> If you have made improvements to your SMS template, can you share what you
> have done?
>
> Thanks,
> Michele
> --
> Michele M. Morgan, Technical Assistant
> North of Boston Library Exchange, Danvers Massachusetts
> mmor...@noblenet.org
>



-- 
Benjamin Shum
Evergreen Systems Manager
Bibliomation, Inc.
24 Wooster Ave.
Waterbury, CT 06708
203-577-4070, ext. 113

Re: [OPEN-ILS-GENERAL] SMS Hold Notifications

[Thomas Berezansky]

I had considered some different ways of getting more information into  
the replies, but generally the gateways don't let anything useful  
through on the response. Or more specifically, the gateways don't see  
it as a response in the first place but rather as new message.


The only option I came up with was to mess with the "From" address,  
but that means every notification will generally end up as a new  
"conversation" from a new sender and patrons can't flag the notices  
properly for special handling on their device.


--
Thomas Berezansky
Assistant Network Administrator
Merrimack Valley Library Consortium
4 High ST, Suite 175
North Andover, MA 01845
Phone: 978-557-8161

Re: [OPEN-ILS-GENERAL] SMS Hold Notifications

[Jason Etheridge]

I've seen one example where the library sends a tiny URL that expands
to the TPAC's My Account page.  Don't know how URL's typically render
when sent via SMS, though.

-- 
Jason Etheridge
| Community and Migration Manager
| Equinox Software, Inc. / The Open Source Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: ja...@esilibrary.com
| web: http://www.esilibrary.com

[OPEN-ILS-GENERAL] Upcoming Documentation Interest Group Meeting: Thursday, November 5, 2015

[Yamil Suarez]

Hello everyone,

The Evergreen Documentation Interest Group has its next meeting
scheduled for Thursday, November 5, 2015 at 2:00 PM EST on the
#Evergreen IRC channel (http://evergreen-ils.org/irc).

Anyone interested in documentation is welcome to attend. An agenda has
been posted at 
http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meetings

Changes and additions to the agenda are welcome.


Here are the links to access the Meetbot formatted minutes of the
previous meeting.

(Meetbot) Minutes:
http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-10-01-14.00.html

IRC Log:
http://evergreen-ils.org/meetings/evergreen/2015/evergreen.2015-10-01-14.00.log.html


Thanks,
Yamil

P.S. For viewing all upcoming Evergreen community meetings scheduled:

http://evergreen-ils.org/communicate/calendar/

You can also subscribe to the various community calendars so that the
meetings automatically appear in your calendar.