Archive for the ‘mobile reference’ category

Using a Mobile / Cell Phone for SMS Text Message Reference Services at Your Library: Thoughts for Consideration

August 6th, 2009

Martin Cooper: Invented the cell phone

Why can’t we just use a phone to handle SMS reference services?

We get that question a lot. It is a great question seeing as mobile phones provide the “truest” form of SMS communications – similar to listening to a vinyl album on a record player.

Our answer usually goes something like this: You can…BUT… given the emerging library technologies available to manage text message reference, mobile phones are very inefficient by comparison.

As we have highlighted before, text messaging is now the preferred method of communication for Americans on the go. Libraries have the opportunity to connect with patrons anywhere (and vice versa) with SMS. The features and functionality of services that are built to manage text messaging without a phone are making the entire SMS reference experience better from librarian to patron, and including administration.

Here are some of the points we reference when answering this FAQ

* Texting vs. Typing
Texting is not and will never be faster than typing. Mobile data speeds will never be faster than internet speeds. Phone processors will never be faster than computer processors. As an efficiency tool, the mobile phone will never match a computer. Even if you personally send and receive twice as many text messages per day than the average American teenager, it doesn’t mean your associates do.

* Single-user access.
1 phone = 1 librarian, answering 1 question at a time. Receiving and responding to SMS patron inquiries using a mobile phone eliminates any possibility of efficient collaboration.

* Reporting is nearly impossible.
We say “nearly impossible” because mobile carriers will send a bill every month and users can see how many messages were sent and received, time/date/etc, but all data must then be entered somewhere else manually. The other option is maintain an ongoing call log, which is also manual and sounds as fun as filling out a time-sheet to prove you’ve been at work from 8-5 all week.

* Text message transcripts via mobile phones are non-existent.
We don’t know of any phones that allow a user to download text message conversation transcripts. They can be manually typed out, or some phones allow forwarding individual text messages to an email, but not entire conversations, so it would be necessary to send multiple messages to an email account, piece them together into a conversation, then upload them to a database. If this is not done, then there is no archive or living database of the types of questions received and answers given.

* Patron history is extremely limited.
Referencing past patron questions on a phone is not an option as a phone’s SMS inbox gets full. If old texts are not deleted, new texts will not be received. Once again, entering transcripts manually is the only solution.

* Phones are not collaboration-friendly.
Some people are better suited at answering certain questions than others. If those people are standing right next to you, you’re in luck. If not, the process you have to go through to get them to help you assist a patron is, at best, an inefficient challenge involving several pieces of technology. The only exception to this is if you literally throw the phone to that person, which can be done, but brings up the next point.

* Mobile phones break, get lost, stolen, need charging and become obsolete.
If you think this is a weak point then please feel free to move ahead to the next one. That said, there’s a strong likelihood that 1 of the above, if not all, has happened to your phone. Stuff happens, and when it happens to your phone, other stuff needs to happen causing a disruption in the very service you are aiming to provide.

* Patron privacy and security
The fact is that mobile phone number confidentiality plays by a different set of rules than email or IM. As an organization, it is important to determine the limits of your library’s liability by storing patron phone numbers on a handheld device that could get lost, stolen or hacked.

* Phones lack easy answer template options for FAQs.
Imagine having to text your library hours time…and time…and time again. Sure, you can save a draft of a FAQ or access a word doc in your phone, then copy and paste – if your phone allows these functions – but it’s pretty obvious that is not the best use of anyone’s time.

* Technical and customer support is not dedicated, quick or easy.
To some people, calling mobile carrier support gives the same feeling as visiting the DMV. Best to have a good book available. Regardless of what your feelings are about the customer or technical support of your mobile carrier, if something goes wrong, you just want it fixed as quickly as possible. While some carriers are known to have better customer service than others, we’ve never heard anyone talk about it being a quick or pleasant experience. Keep in mind, mobile carriers handle their service only. Technical support for the mobile phone itself is handled by the manufacturer.

* Phones are not scalable.
As the popularity and use of your SMS reference service increases, so do issues related to management, collaboration, reporting and efficiencies as mentioned throughout this post.

* Phones are not that cost-efficient.
We can’t possibly list all of the phones and plans available by mobile carriers, but there are some simple costs of using a phone to consider. Using a reliable mobile phone carrier (getting good reception in the library) with a QWERTY keypad is the first place to start. Basic math on the most stripped down phone & plan = Price of phone + Price of plan(s) + Activation Fee + Taxes + Insurance.

After taking some time to research phone costs, consider the cost of your or your staff’s time: texting rather than typing, transcribing SMS reference conversations, compiling data for statistics and reporting, waiting on hold with carriers or manufacturers if something happens to the phone or service.

If you’re wondering, here’s the cheapest cost for an iPhone on AT&T:
iPhone 3G (old) – $99 or 3Gs (new) – $199
One time activation – $36
Data Plan (required for life of phone) – $30 per month x 12
Voice Plan (min. voice plan required) – $40 per month x 12
Text Message Plan ($5 / $15 / $20) – $15 per month x 12
Taxes – $3 per month x 12
Insurance – $5 per month x 12

TOTAL = $1251 per year x 2 year contact = $2502

[By the way, we LOVE iPhones. We have them and Text a Librarian works great on both the iPhone and iPod Touch. That said, every issue presented above applies to the iPhone.]

In case you are still reading [enter crickets chirping], there’s one more thing to consider: Companies that build services for libraries have a vested interest to make sure their solutions are the best available for librarians. The good ones listen to feedback and not only respond, but anticipate, changes and trends in technology in the library industry.


Bookmark and Share

Thanks for reading.

Ps. We realize that there are some libraries out there that are currently using a mobile phone to handle SMS reference. If it is working for you and your library, great! That said, if you are now looking to implement text message reference, it’s worth weighing all options to determine what will work best for your library and staff.

Beyond 160 Characters in the Library – Text Messaging Reference Doesn't Need to Be Limiting

July 20th, 2009

Many, many, many...

There seem to be varying stories about the history of SMS (Text Messaging) and why Friedhelm Hillebrand, the creator of SMS, decided on 160 as THE number. Some say it’s the amount of characters on a typical postcard, many other stories not that he just determined it while sitting at his type-writer in Germany, noting that most sentences do not require more than 160 letters. In many blog posts and mentions about using text messaging reference in the library, we see it noted that phones are limited to 160 characters. While this statement is mostly true, some phones and carriers let users extend their messages, this limitation only hinders your ability to respond to patron questions based on what method you are using to respond to them.

Without getting into the various ways you can respond to a patron inquiry to extend your response beyond 160 characters, suffice it to say each system has its own unique solution, most requiring more manual work on your part. Instead, let me explain how Text a Librarian solves that problem and makes it significantly easier for librarians: character counters and multi-message splitting.

Mosio's Text a Librarian enables you to send text message responses beyond 160 characters.

Mosio's Text a Librarian enables you to send text message responses beyond 160 characters.

Character Counts and Multi-Message Splitting
Text a Librarian has a real-time character counter and message view so you can see exactly what the patron’s text message is going to look like as you type it out in the answer box. If you type beyond 160 characters, the system shows you what the second message will look like and will send it as such, extending the space you have to send a thoughtful and well-formed response. It seems relatively simple and it was built to be that way, but it is a necessary functionality to make it easier for librarians to respond while offering patrons the most helpful and content-rich answer they can get on their mobile device.

Which is More Important: The Patron Experience or Librarian Experience?
Our answer? Both. In speaking with anyone on the Mosio team, you’ll often hear the phrase “patron experience” or “librarian experience” when it comes to our system and interaction design. Simply stated, we don’t see a reason to offer a reference service if it’s going to be difficult for patrons or librarians to use, no one is going to get excited about it. In fact, a handful of people ask “why don’t you have the page auto-refresh when a new question comes in?” It’s a valid question and we initially integrated it. Then we tried answering a question when another question came in. The page becomes a moving target and the assumed convenience of having a new question magically appear on the page becomes frustration at the inability to answer the question you’re working on.

The product team is working on a few additional features that will take mobile reference even further, providing a richer experience to both patrons and librarians, enabling both to get excited about its simplicity and ease of use. For the time being, this functionality is being well received by our libraries using the system, expanding the character limitations within the core technology.


Bookmark and Share

Mosio's Text a Librarian Thanks J.B. Hill – The Pioneer of Text Message Reference in the Library

July 6th, 2009

Was reading through some old posts about the subject recently and wanted to take a moment to recognize and thank J.B. Hill from Southeastern Louisiana University, for being the pioneer of text message reference in libraries. The Librarian in Black recognized him in a post back in November of 2005 and we just want to take a second to thank him again for getting the mobile medium utilized in the library. During that time, Mosio was in its infancy, Text a Librarian.com not yet launched, we were exploring how to build a scalable system enabling people to text in questions and get answers quickly. A lot has happened since then, our platform has won some awards and more and more libraries have implemented SMS reference in various ways. We look forward to watching (and being part of) the evolution of mobile libraries and the extension of these types of services to patrons, making libraries an even more powerful resource in the search for information.

Hats off to you for getting this started!

Hats off to J.B. Hill, Pioneer of Text Messaging Reference (from Mosio's Text a Librarian)

Hats off to J.B. Hill, Pioneer of Text Messaging Reference (from Mosio's Text a Librarian)


Bookmark and Share

Social Networks, Web 2.0 Services and Collaboration Tools in the Library

July 2nd, 2009

I’m fascinated by the new report from Robin Hastings, Collaboration 2.0 and I haven’t even read it yet. My fascination with it is the fact, and I’m not really too surprised given the library industry, that a report has been written to help library managers make a case for utilizing social networks to increase outreach and collaboration. I think it’s great! A company I founded and still a partner in banned instant messaging for employees while at work. Even though the company is spread over offices in 4 cities with collaboration being a necessary part of every day, the thinking was that people spend too much time chatting and not enough time working. As against the policy as I was, I don’t “work” there anymore, so I let it go. There was no uprising, there was no coming together to make a case for why things would be better, no reports written to arm employees with the info they needed to make a case, mostly posts on how to circumvent firewalls or philosophic questions about whether or not it should be allowed. Then again, these employees weren’t and are not blocked from those sites, they were just told it was against company policy.

Text a Libarian is about to launch a new service we call RefStart. It’s a web application combining virtual reference with social media and search, giving librarians one-click access to the web 2.0 tools they like best. I say “like best” because the fully flexible system lets them choose, so if they use Facebook, Twitter, Delicious, Flickr and Google, for example, the system let’s users quickly link to those pages while notifying them on the page when a new text message reference comes in through our system. The initial reaction we’ve received about the feature has been very positive, but I’m curious to see which librarians will see it and say “well this is great, but we can’t use Facebook or Twitter.” It won’t matter either way because they can simply choose elements of their page that don’t access those (or other) banned sites, but it’ll be interesting to see how many come forth with that info.

My favorite thing about working at Mosio / Text a Librarian is that the day-to-day energy of this place is in the creating solutions, solving pain points, making reference librarian’s day-to-day tasks easier. This isn’t lip service, everyone here loves what they do. We ask, we watch, we listen to librarians in trying to find out what will make not only the best text messaging reference software in the industry, but how we make it the best virtual reference software on the planet. This way of thinking fosters innovation, it’s what made the development team come up with an optional, pleasant audible noise when a new question came in because a library customer wasn’t allowed to use IM. The task was fun: “What does an incoming question sound like?” We found a great one, then got a request from the same library that the sound was SO pleasant that it blended in with the ambient noise of the library. Their request? “Just below the level of foghorn. How about some Led Zeppelin? ;-) LOL” Awesome.

I’ll loop back and re-post about how the experience goes, but whether or not those we talk to are able to access Facebook, Twitter and the like, RefStart will be there and work well. After reading Robin’s report, armed with the tools librarians need to gain access and open up outreach to the new web 2.0 technologies being used by thousands of other libraries, they’ll be able to update with no problems.

Mosios Text a Librarian - Mobile reference simplified. RefStart Image.

Mosio's Text a Librarian - Mobile reference simplified. RefStart Image.


Bookmark and Share