NISO Webinar: Content on the Go: Mobile Access to E-Resources
- 1. http://www.niso.org/news/events/2012/nisowebinars/
mobile_access_to_eresources/
Content on the Go: Mobile Access to
E-Resources
August 8, 2012
Speakers: Carmen Mitchell, Institutional Repository
Librarian, California State University San Marcos:
Eleanor Cook, Assistant Director for Collections &
Technical Services, East Carolina University;
Marty Picco, Director of Product Management, Atypon
Systems
- 2. Challenges to
Consider
Developing Mobile Access to Digital
Collections
- 3. Background
Initial survey done July 2010
Original survey: http://goo.gl/1ujA.
25 respondents. Presented results at
CurateCamp, UC Berkeley.
Approached smaller group for more in-
depth case studies:
7 questions
4 organizations
All doing active development of mobile apps
or mobile websites
http://www.dlib.org/dlib/january12/mitchell/01mi
tchell.html
- 4. Participants
Tito Sierra, Associate Head, Digital Library
Initiatives North Carolina State University
Libraries (currently Associate Director for
Technology in the MIT Libraries)
Jason Clark, Head of Digital Access and
Web Services at Montana State University
Libraries
Sean Aery, Web Designer, Digital
Experience Services Dept., Duke University
Libraries
Nancy Proctor, Head of mobile strategy and
initiatives for the Smithsonian Institution
- 5. What is the appropriate approach for development of mobile access to
digital collections?
Varies by organization:
Look at population and analytics first.
Just because you *can* create a mobile app or website
doesn‟t mean that you should.
What is the added value for patrons?
Moving target – the only constant is change.
Is mobile content/access a part of your strategic plan?
How to scale?
Utilize current infrastructure to support, if possible.
Be realistic about cost.
Ongoing support, staff time?
- 6. What would you have done differently/lessons learned?
Learn not to freak out at the first bit of criticism.
Consider access:
“Products developed for access always revolutionize
everything else we do.”
Working within mobile development requirements makes you
ask tough questions about needed features and forces you to
streamline and optimize your code in a good way.
Deploying an iOS app can be complicated.
Not worth investing too much time in any specific framework
or architecture, as it is likely to become outdated in 6-12
months Nimbleness is a virtue.
Timely innovation can be good PR.
- 8. E-books on the go: How a university
library experimented with E-book
readers
Eleanor I. Cook,
Assistant Director for Collections & Technical
Services, East Carolina University
NISO webinar, August 8, 2012
- 9. Quick “About”
• 3rd largest university in UNC system – 27,000
students, 5,000 staff & faculty, Doctoral/Research +
medical & dental schools
• Joyner Library serves all academic disciplines except
Medical/dental served
by Laupus Health Sciences
Library
• Serves the far eastern
region of NC
- 10. Time line
• May 2010: 1st purchased Kindles, Nooks & iPads
• Summer 2010: Devices used by staff to gain
familiarity with them
• July 2010: 1st content acquired (Kindle & Nook)
• August 2010: Faculty & Staff Petting Zoo held
• Fall semester 2010: Kindles & Nooks roll out
• January 2011: iPads roll out
• March 2011: Ebook Expo held on campus
• Spring 2011: Color Nooks & newer iPads purchased
• Summer 2012: All original Kindles & Nooks replaced
with new models
- 11. Cross-Departmental Collaboration
• Library Technology Division: Acquires devices, registers & sets
them up, applies inventory controls (property tags, barcodes for
ILS), sets up wireless access, troubleshoots tech problems after
devices begin circulating; maintains spare parts inventory
• Collection Development: Decides budget for content, weighs in
on content selection
• Acquisitions: Purchases content, manages credit card
reconciliation and tax refunds, triggers communication chain each
time content is purchased
• Cataloging: maintains public list of content, catalogs each title as
purchased
• Circulation: Circulates devices, maintains patron license
agreements, loads new content as directed by Acquisitions, reviews
devices regularly for damage, rogue content, or other problems;
works with Lib Tech when readers malfunction
- 12. Types of Content
• Popular reading titles, both fiction and non
• Special request from a faculty group who
needed specific content on a rush basis
• Freshman reading titles being considered
• Special request for an audio book
• Free classics and a few games
- 13. Circulation policies & issues
• 2 week checkout – like Popular reading
• User signs liability agreement when checking out
the device
• Staff check for all pieces when returned, check for
damage, check for content
• Sometimes users load free content – we remove
periodically, if it is inappropriate – varies by e-reader
• Occasional problem w/users buying their own
content, wiping out content, etc.
- 14. How they are cataloged
• Master bib record for each kind of device with
item records for circulation purposes
• Contents note on master record
• Individual title bibs for content that are
“linked” to the device bibs
• Took some experimentation to decide which
approach to take with the cataloging; better
too much than not enough!
- 17. Early conclusions
• Content loaded only on Kindles & Nooks since
adding content also to iPads took up licenses
• Sales Tax issue problematic but made doable
(at this scale at least)
• Use by patrons primarily for leisure reading
and comparison shopping
• Neither company really cares about library use
at the level we are doing this
- 18. Later Conclusions
• Basic device models easier to manage than hybrid
tablet models (Kindle Fire & Color Nook)
• 2012- will load different content on Nooks & Kindles to
get more content for $$ spent
• Both types of e-readers are popular though some
people prefer one or the other
• iPads very popular also but for different uses
• Companies started offering new models of purchase to
libraries after awhile, but those arrangement are
negotiated
• Mobile is here to stay!
- 20. A Few Useful Sources
• Cook, E. I. (2011). “Chapter 3: Academic Library Dilemmas in Purchasing
Content for E-readers.” Library Technology Reports, 47(8), 14-17. [The rest
of this issue is also devoted to topics about E-book use]
• Dobbin,G., Dahlstrom, E. and Sheehan, M.C. (2011). The ECAR Study of
Mobile IT in Higher Education, 2011.
http://net.educause.edu/ir/library/pdf/ers1104/ERS1104.pdf
• Not Shelf Required - http://www.libraries.wright.edu/noshelfrequired/
This is the Blog
• Polanka, S. (2011). No shelf required : e-books in libraries. Chicago: ALA.
• Polanka, S. (2012). No shelf required 2: use and management of electronic
books. Chicago, ALA.
• Sapon-White, R. (Jan. 2012). “Kindles and Kindle E-books in an Academic
Library: Cataloging and Workflow Challenges.” Library Resources &
Technical Services, 56 (1), 45-52.
- 21. Screen shot examples
• Example of Kindle record
• Example of Nook record
• Example of an individual e-book record
• These links will actually take you to our
catalog records in case you want to explore
more in depth
- 23. Strategies for Mobile
Content Delivery
Publisher Perspective
Marty Picco
Director of Product Management
Atypon
Content to Go: Mobile Access to e-Resources August 8,
2012
- 24. Atypon - Literatum
• Leading platform for professional
and scholarly publishers
• 12.5 million journal articles
• 50,000 eBooks
• Towards 1.4 B user sessions in
2012
Strategies for Mobile Content Delivery
- 25. Literatum for Mobile
• Launched in Fall 2010
• Working on 3rd generation
• More than 3200 mobile journals
• Nearly 1 M active mobile users
Strategies for Mobile Content Delivery
- 29. Web App vs. Native App
• HTML5 is cross platform choice
• First rate features and
performance
• „Get the app‟ is annoying
• Native can have a role
• User relationship is key
Strategies for Mobile Content Delivery
- 33. Advantages
• Viable for all institutions
• Easy for end-users
• Secure for publishers
• Automatic pairing now available
Strategies for Mobile Content Delivery
- 36. Tablets
Lean-back
experience
Big
Unique interactions
enough
for work
Strategies for Mobile Content Delivery
- 38. Dig
Browse Search Read
Information forward
Strategies for Mobile Content Delivery
- 40. Search and
Recommendations
• Automatic topic modeling
• Similarity to research intent
• Serendipity
Strategies for Mobile Content Delivery
- 41. Annotations
• Available on any device
• Portable, stay with user
• HTML or PDF
• Highlight, comment
• Open Annotation W3C Group
Strategies for Mobile Content Delivery
- 42. Social
• Personal & professional separation
• Public and private groups
• Share articles
• Share annotations
Strategies for Mobile Content Delivery
- 43. Everybody Wins
• Mobile becoming central to users
• Everywhere, accessible, readable
• User centric
… delighted users and successful
publishers
Strategies for Mobile Content Delivery
- 44. Thank you!
Marty Picco
@martypicco
mpicco@atypon.com
linkedin.com/in/picco
Strategies for Mobile Content Delivery
Editor's Notes
- iOS alone won’t get you thereAndroid is actually at forefront, esp. internationallyAndroid fragmentation is a serious issue
- HTML5 Write once, run anywhere not really true but massively better than alternativePerformance YMMV but getting better fast Nexus 7 -> Chrome yea!Get the app How do users land on page? Google or App Store?Native Role API makes native possibleAppStore sales model limitationsUser relationship: improve recommendations, target messages, access to user info (favorites, annotations) everywhere
- IP range: people move around; 3G/4G networks use different IPs, even within authorized institutionsShibboleth/Athens: incomplete control of user experience; takes user out of app to website that might not render effectively on mobile devicesMany users rely on institutional access and do not have personal accounts
- Take advantage of uniquely personal nature of mobile devicesFirst generation – needed user action
- Repurpose XML
- User directed, not publisher directedPublisher and institution suggestions
- Putting all the aspects together increases user satisfaction and usageGood for publishers, institutions, authors … everybody!