Presentation on theme: "MOBILE TECHNOLOGIES: ISSUES FOR ACADEMIC LIBRARIES Elsevier Digital Libraries Symposium ALA Midwinter 2011 Brian E. C. Schottlaender The Audrey Geisel."— Presentation transcript:
MOBILE TECHNOLOGIES: ISSUES FOR ACADEMIC LIBRARIES Elsevier Digital Libraries Symposium ALA Midwinter 2011 Brian E. C. Schottlaender The Audrey Geisel University Librarian UC S AN D IEGO
The mission of the UCSD Libraries is to be leaders in providing and promoting information resources and services to the UCSD community when, where, and how users want them. ||| BECS |||EDLS W HY G O M OBILE ?
According to the Pew Research Centers Mobile Access 2010 (July 2010): – 40% of adults use the Internet, or instant messaging on a mobile phone (up from the 32% of Americans who did this in 2009). – 65% of year olds access the Internet on their mobile device – 43% of year olds access the Internet on their mobile device ||| BECS |||EDLS W HY G O M OBILE ?
In a 2010 Library Journal survey, respondents from almost 500 academic and public libraries cited the following reasons for their reticence about going mobile: – Priorities – Budget – Perception – Skills ||| BECS |||EDLS P ERCEIVED B ARRIERS TO E NTRY FOR L IBRARIES
Provide a simple, clutter-free interface. Dont try to mobilize all our library services. Dont recreate the wheel. Adopt a rapid and modular approach to mobile site development. Dont develop for a specific device, but also dont bog down developing for every device. ||| BECS |||EDLS O UR T HOUGHTS G OING I N
6 UCSD L IBRARIES M OBILE ||| BECS |||EDLS
7 UCSD L IBRARIES H OME P AGE ||| BECS |||EDLS
8 UCSD L IBRARIES M OBILE ||| BECS |||EDLS
||| BECS |||EDLS UC R IVERSIDE S M OBILE WCL
||| BECS |||EDLS BYU S M OBILE F LOOR P LAN
||| BECS |||EDLS O REGON S TATE S PC A VAILABILITY …
||| BECS |||EDLS … AND T HEIR M OBILE C OFFEE L INE
Priorities : This is largely an administrative issue, and speaks to Perception as well. The thought here is that users are not demanding mobile services, so its not a library priority. However, if we wait until user frustration is high enough to reach everyones ears, then weve probably missed our opportunity already. Budget : In dire budget scenarios, the prevailing attitude is often to hold the line with existing services. At the same time however, mobile device usage continues to skyrocket in spite and independent of library budget woes. So it could be argued that going mobile isnt just a luxury for libraries with extra money, but rather a priority for all libraries. Of course, going mobile costs money to establish and maintain. But the cost of doing so is going down significantly as in-house development tools improve, and as more vendors offer off-the-shelf services. [ Brian- I could provide lots of examples of these if you want ] Perception: The belief here is that either mobile internet usage is more of a fad than a fundamental shift, or that our existing services are already adequate for users. I think the assumption (and a false one) is that because traditional library services (walk-in, , telephone, and website) are successful, they will remain so, and users will not seek us out via mobile. Skills: The concern here is a perceived lack of staff technology skills to develop and maintain a mobile presence. UCSD Libraries are fortunate to have robust in-house tech talent, but many libraries do not. For this concern, I would note that the number of 3 rd party and off-the-shelf options is expanding rapidly. While you may not get the level of control you want, its really no different than outsourcing OPACs or ebo ||| BECS |||EDLS Why these concerns are not as large a barrier as imagined
Provide a simple, clutter-free interface. Dont try to mobilize all our library services. Instead develop the ones likely to be most useful to a mobile user. Dont recreate the wheel: look at what popular and successful mobile services are being offered by other libraries, and develop those first. Adopt a rapid and modular approach to mobile site development. That is, roll out the services with the largest user benefit first, then add new services as they are developed. This approach differs from that typically used in full-size library Web site, in which every component is created first (and often slowly at that), then rolled out in one big package. Dont develop for a specific device, but also dont bog yourself down developing for every device. For example, the rage used to be to develop just iPhone apps. Now Android-based phones are coming on strong in the market, but these devices cannot take advantage of iPhone-oriented apps. Conversely, if you try to create a site that works well for every flavor of Smartphone, youll never get the site finished. Our mobile site works is optimized for iPhones and Droids, because those are what the vast majority of our patrons use. ||| BECS |||EDLS O UR T HOUGHTS G OING I N