Top Ten List: Number Three

From the Library Technology Conference, in reverse chronological order:

3. Go Mobile with Your Library Website, Meghan Weeks, Loyola Marymount University

• Why go mobile? Many reports indicate the increase in the use of mobile technologies is on the rise and here to stay (the presenter noted studies by the Pew Research Center, Horizon Report 2011, and the Educause Center for Applied Research (ECAR) Study of Undergraduate Students and Information Technology, 2010). Mobile technologies are increasingly becoming a student's first choice.
• Things to consider: Is your library website ready? What do your users want? Surveys may be an effective way to determine which features you need to include in your mobile website, though the speaker did not mention focus groups (which could be quite helpful, as was the case of the Kent State library).
• Features to consider:
  
  • Direct link to call
  • Link to text message ("Ask Me" instant messaging)
  • A customizable mobile environment--What are the tools/resources each individual patron uses most frequently? Can they add that to their customized mobile library page?
  • LibGuides mobile interface
  • Ebsco and other mobile databases
  • The ability to reserve spaces (i.e. group study rooms, computers with specialized software, scanners, etc.)
  • Perhaps a library QR code tour or podcast
  • Encourage interaction with the library's social media presence
  • Easy access to e-books, streaming videos/music on demand
• Programming considerations from the library's end:
  
  • Are you willing to write native apps (specific to each type of device: Android, Blackberry, iPhone)? The benefits of this are that it is easier for users to navigate, faster than mobile web, and the app can capitalize on device features (i.e. GPS). Having an internet connection may or may not be necessary (bandwidth), and the apps are usually written in Objective-C or Java. Updates do need to be installed, and the program does need to be marketed in app stores (which means it is up to users to download).
  • Would you rather scale down your website to be accessed using a smaller browser, taking a mobile web approach? Things to keep in mind when using this approach are that the page needs to be optimized for use on a smaller, mobile device. Also, there is the need to connect to the server. Usability tends to be lower because of the many steps it takes to navigate the links and time it may take to connect via a server. Programming is typically HTML, with CSS and Java. While mobile web sites tend to be designed with simplicity in mind, they are not targeted at one specific platform, making the user experience less customizable. The benefits include the ease with which such websites are created and maintained, and that the user does not need to install updates as they might with apps.
  • The hybrid approach (combining apps and mobile web) may work best for some libraries. The app is installed on the mobile device, is platform specific, and can utilize device features, but some of the areas accessed may be mobile web. Some features may need to be periodically updated (app) but some will be instant (and require network access).
• Names to know when it comes to integrating a mobile version of your website into your offerings:
  
  • MOPAC: Mobile OPAC is a customized catalog for mobile devices. AirPAC, by Innovative Interfaces, is one example. Another is the Mobile PAC by Polaris Library Systems.
  • BookMyne from Sirsi Dynix offers library users with iPhones the ability to scan bar codes (to see if the item in the store or at a friend's house is available via the library), social recommendations powered by Goodreads, the ability to cross-reference books in the library with the New York Times best sellers, and the ability to view their account information (i.e. fines, fees, current holds, checked out items). Libraries running SirsiDynix Symphony 3.3, Horizon 7.5 or higher may use BookMyne.
  • Discovery services include: Primo by Ex Libris, Serials Solutions Summon, and EBSCOhost Mobile.
  • Third party vendors include Blackboard Mobile Central (an app with a library portion to it, very limited, just one page of information and no access to user library account information), Boopsie for libraries (users can log in, place holds, renew items, and the app utilizes phone model features), Library Anywhere (by Library Thing), and Mobile Bridge (by Quipu Group).
  • Open Source options include the Washington D.C. Public Library iPhone app, Molly (the opens source mobile portal from Oxford University), or librarians may develop their own apps.
• Usability considerations: Just as we consider those with disabilities in designing standard HTML websites, we must also do so with mobile pages. Issues with typing, viewing, etc. occur. The W3C has released their Mobile Web Best Practices 1.0; their aim "is to improve the user experience of the Web when accessed from such [mobile] devices." Other testing tools include EvalAccess 2.0, and Mobi Ready.
• Analytic tools: chartbeat, Clicky, Google Analytics for mobile, Piwik, and Sitemeter.
  
• App development tools: Appcelerator, Mother App, Netbiscuits, PhoneGap, and Rhomobile.


• Mobile helper utilities: Skweezer.com, Mobile Site Generator, iWebkit, Google App Engine, and JQTouch.

Article Discussion: Library on the Go: A Focus Group Study of the Mobile Web and the Academic Library

Seeholzer, J. & Salem, J. A., Jr. (2011). Library on the go: A focus group study of the mobile Web and the academic library. College & Research Libraries. 72(1), 9-20.

The authors examined the use of mobile Web technologies and design at Kent State University. Their literature review showed an increase in mobile device Web use. This only makes sense as smart phones (and plans) become more accessible and affordable. While “librarians are already using the mobile Web to deliver library instruction, access book and audiobook collections, conduct audio tours, send out text message notifications, and provide reference assistance,” there were no published studies about how mobile Web is used by library patrons, and how libraries created their mobile Web sites for patron use.

The librarians at Kent State organized four focus groups (one pilot group, three focus groups), comprised of Kent State students (both undergraduate and graduate). These students were recruited in a variety of ways, including online ads, flyers around campus, and word of mouth. Students received lunch and $10 added to their campus debit card for participating. The met in a conference room at the library, where the library’s website was projected, along with other libraries’ mobile websites. The group used an iPod Touch to examine the mobile sites. The same prompts were used throughout the focus groups, and a total of 20 students were included.

The results were fairly consistent across the different sessions. Those topics most focused on were “1) use and perception of the mobile Web by KSU students; 2) library resources for the mobile Web; and 3) other technologies for the library to explore.”

Use of the Mobile Web, Library Resources by KSU Students

Most students had Web enabled devices (phones, iPods, etc.). Those who didn’t “expressed interest in obtaining a mobile device with Web connectivity.” There were varied levels of personal Web device use, but those who did use it often (i.e. daily) tended to favor websites like “Facebook, e-mail, weather, directions and sports sites.” When asked about using the library’s Web page, many noted its value for beginning research (quick) such as looking up call numbers, browsing the library catalog, and database searching (if it were to be made available to mobile devices), but not for in-depth work, which they were more likely to do on a laptop or other computer.

One thing I found interesting was the authors’ findings in regards to which parts of the library website students see as most useful on their mobile device (i.e. research, services, about us). “Surprisingly, a number of participants identified research databases as an essential element of a mobile version of the Libraries’ Web site...Even after participants were informed that research databases would most likely not be formatted for mobile devices, they still expressed interest in having these tools available from the library’s mobile site,” to be able to begin their research from anywhere, during pockets of free time. Also of great interest, under the “Services” section of the Web site, are Course Reserves and the ability to check the status of their account (due dates, holds). Though librarians anticipated students to show great interest in the mobile “About Us” page, few students were interested in the details found there (hours, locations and directions, staff directory), and were more interested in an explanation of using call numbers or a guide to finding books on the shelf. Also, “participants identified the ability to contact a librarian as being of prime importance.” Having the “Contact Us” button was emphasized, whether the contact happens through texting or through a web interface, having librarian help wherever the students were was an important part of the service. “About Us” was ranked last when students were asked to rank aspects of the Web site.

Students were also given the opportunity to discuss “other features they would like to see the library provide on mobile devices.” Not surprising, improved functionality of the library’s catalog, the ability to personalize and customize (i.e. accounts), and texting questions to librarians were all mentioned. For the catalog, searching, putting items on hold, renewing items, having text notifications sent when requested items are available, and library appointment text reminders (meetings with librarians/library events/upcoming project deadlines).

Briefly mentioned was mobile site design. The students indicated the “bare bones” site felt lacking compared to other mobile sites with which they were familiar. Also, limiting the number of links on the mobile Web site for simplicity and usability is important, but also including a link to the main Web site was important (in case they weren’t able to find what they need on the mobile site; using it may be clunky, but if it has what they need, they’ll use it).

In the future, the librarians at Kent State want to continue to have student input when planning Web reviews; further qualitative research needs to be done and published, adding to the professional literature.

This was interesting to read and generally apply some of the ideas introduced in the article to our discussions about the University of Dubuque’s “How do I...” webpage (similar to many FAQ pages). We are thinking about a variety of populations we are serving/targeting with this one page, design concepts (how to make it useful, concise but informative, and clean & easy to use). We’ve started examining other libraries’ websites, noting those things we like, what we might adapt to meet the needs of our users, wording, coding, searching, etc. At this point, the UD library’s website has to fit within the framework of the large University’s design and lay-out standards but, keeping that in mind, we are still able to be flexible with our approach and design that we will discuss with the University library Web liaison.