Presentation given on 22 January 2014 at Jisc Collections Mobile Resource Issues: Publisher workshop

1. Mobile Access
What do libraries want?
Claire Koch
Virtual Support & eServices Developer
University of Surrey

2. Background
• Queries about apps being advertised on
publisher sites
• Queries about how to use certain apps
• Increased use of mobile devices around
the library

3. Background
• Increased access of Library website on
mobile devices
Mobile access
60000
50000
40000
30000
20000
10000
0
2010-2011
2011 - 2012
2012 - 2013

4. University of Surrey Mobile project
Aims to improve access to our resources and information from
any device, anywhere
Library resources
• Library website
• Maps
• Information
• Booking systems
Supplier resources
• eBooks
• eJournals
• Databases
• Catalogue/Discovery

5. Devices
Images from Wikimedia Commons

6. Investigating useful apps
• 170 Providers checked:
• 17 had mobile optimised sites only
• 28 had apps
• 14 had usable/useful apps

7. Would you access eResources on
your phone/tablet?
No
If it was
mobile
friendly
Yes
If there
was an
app

8. How would you like to access
eResources on your phone/tablet?
I don't
want
to
From the
Library
website
From a
University
app
On a mobile
friendly
publisher's
website

9. What do students &
libraries want?

10. We want it to be
• Easy to use
• Easy authentication
• Easy to search and browse

11. Authentication options
•
•
•
•
•
Athens/Shibboleth/Institutional Login
Device pairing/twinning
Activation key/login
Social Media
IP Recognition

12. We want it to be
• Clear instructions
• Clear whether you are logged in or not
• Clear distinction between full text and
summary only articles
• Clear navigation

13. We want it to be
•
•
•
•
•
Fast to load
Full text availability
Ability to download full text to read offline
Ability to export citations
Accessible

14. We want it to be
• Students already pay fees
• Libraries already pay for subscriptions
• Unless offering new/extra content, it should
be free to students

15. We don’t want…
• Unclear and inconsistent authentication
options
• Authentication that requires you to be on
campus
• Apps that crash
• Apps that don’t provide full text
• Apps that are just marketing tools with no
content

16. Summary
• All publisher websites should be mobilefriendly
• Apps should have full text, clear
navigation, easy authentication and should
be fast

17. What would make a brilliant app?
“Only ask for login details once”
“Clear sign-posting”
“Speed it up”

18. Thank you!
Claire Koch
Virtual Support & eServices Developer
c.koch@surrey.ac.uk
@claire_joanne
Claire Gravely
Information Resources Advisor
c.gravely@surrey.ac.uk
@library_claire