[Workflowtoolkit-l] ILLIAD notification as text messages

Wed Mar 14 09:49:00 EDT 2012

In regards to messages being too short. Can you just say. "You request has been cancelled, follow this link to see the reason http://cancellationreason.htm"?

Jim Cummings
Interlibrary Loan Borrowing Assistant
J. W. England Library
4200 Woodland Ave
University of the Sciences in Philadelphia
Philadelphia, PA 19104-4495
215-596-8969
215-596-8760 FAX
DOCline/OCLC: PAUPPS/PCP
Ariel: ariel.usp.edu
Odyssey: illiad.usp.edu
j.cummin at usciences.edu | www.usciences.edu
USciences: Where healthcare and science converge.

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Nathan Hosburgh
Sent: Friday, March 09, 2012 4:27 PM
To: 'ILLiad Best Practices Workflow Toolkit'
Subject: Re: [Workflowtoolkit-l] ILLIAD notification as text messages

Sue, I think what you mean is that you've made changes in the ILLiad client?  I'm not sure how you would make changes to each user's email in the CM (unless there is something with ILLiad Exclusive that I'm not aware of).

If you're modifying the email address from w/n the client to be someone at somewhere.edu,10digit#@whatever.com then it should work.  However, I would experiment with some of your colleagues at work and use different syntaxes with the extension (the @whatever.com part) before assuming that it's not working at all.  

This Wikipedia entry is another source of potential sms extensions: http://en.wikipedia.org/wiki/List_of_SMS_gateways

Heather Klish's email explaining how they have incorporated the text messaging into the User Information page at Tufts was very interesting.  I think at any given institution you would want to determine whether the benefits of setting up text messaging would outweigh the potential problems, as described by others. 

Nate

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Sue Gagnon
Sent: Friday, March 09, 2012 3:47 PM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] ILLIAD notification as text messages

I am reading all the responses to my question with great interest.  Nate, I tried sending a message to my cell phone with no success.  Could this be because I made the change to my email field in the Customization Manager.  We don't allow our users to update their ILLiad profiles.  Instead, I have always made changes in the Customization Manager.  We use the ILLiad Exclusive Authentication method so that we batch load users once or twice a year.  I'm not sure if I am explaining myself correctly.  This Friday afternoon has me very sleepy.  

Sue

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Nathan Hosburgh
Sent: Friday, March 09, 2012 3:14 PM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] ILLIAD notification as text messages

These observations are all very interesting.  We've been experimenting with text messaging and seen this so far:

- No email stop signs occur: both standard emails & texts are successfully delivered without errors
- Depending on the phone/provider, the same message may come all in one text message or may be broken up into multiple messages (but with all info intact)
- Some providers have more than one possible extension (10 digit#@whatever.com), so the patron may have to find the right one through trial and error.  For instance, Tracfone has 5 or 6 possibilities.  I could see patrons setting up the text messaging, assuming it didn't work, and forgetting about it.
- Testing with Tracfone, AT&T, Sprint has been successful
- Testing with standard mobile & smartphone has been successful (standard Tracfone actually kept entire email in one text message)
- Not sure why Frank's email field is truncated w/n ILLiad client.  It looks like our client will hold emails of at least 55 characters.  Perhaps it is something with the Web validation?
- I could see how, in general, the standard emails could be shortened to be more concise with less characters & spacing - this may be an improvement for both standard emails & texting.

Thanks for the discussion,
Nate

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Schwartz, Andrea
Sent: Friday, March 09, 2012 2:30 PM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] ILLIAD notification as text messages

Just an FYI.  We implemented text messaging a while ago (over a year, maybe two?).  It is very hard to get the messages (esp. cancellations) short enough for texts and meaningful enough for emails--mine still aren't short enough.  The bigger issue for us is that we get an email stop sign error EVERY time an article delivery notification goes out and we can't figure out why--there's no issue with the loan delivery notices.  Last time I talked to Penn State, they were experiencing this issue intermittently as well.  We only have a few users who signed up for text messaging, but it's still a pain to clear those errors and manually re-send the notices.

Andrea @ PBB

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Frank Haulgren
Sent: Friday, March 09, 2012 1:57 PM
To: ILLiad Best Practices Workflow Toolkit
Subject: Re: [Workflowtoolkit-l] ILLIAD notification as text messages

Ann -
How did you modify your cancellation messages?  These seem like they'd be particularly difficult to convey in 120 or characters.  One thought that occurs to me is that with the unautomated messages like a cancellation or longer email message we could edit out the text address within the client.  But those automated notices would need to be really concise.

Frank Haulgren
Western Libraries, Western Washington University Document Delivery & Collection Services Manager
360-650-7641

-----Original Message-----
From: workflowtoolkit-l-bounces at geneseo.edu [mailto:workflowtoolkit-l-bounces at geneseo.edu] On Behalf Of Penwarden, Ann (ETS: Library)
Sent: Friday, March 09, 2012 10:31 AM
To: workflowtoolkit-l at geneseo.edu
Subject: [Workflowtoolkit-l] ILLIAD notification as text messages

We have done a little testing here at MCC with my phone.  While I like receiving the notifications, the problem is that the email message format is too long so it gets cutoff.  We've done some modifications so that the message still reads fine in email and is understandable in the text, but you will most likely need to edit all of those notifications if you start using text messaging as an option.

Ann

Ann Penwarden
LeRoy V Good Library
Monroe Community College
PO Box 92810
Rochester NY 14692-8910

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l

_______________________________________________
Workflowtoolkit-l mailing list
Workflowtoolkit-l at geneseo.edu
http://mail.geneseo.edu/mailman/listinfo/workflowtoolkit-l