Iet tcm 5th_oct2011


Published on

IET Coffee Morning - 5th October, 2011.

Meeting the needs of Library users on the mobile web

By Hassan Sheikh and Owen Smith
The Open Unviersity Library, UK.

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Library has a physical building but it is mainly used by the staff and research students on campus plus by a small number of walk in users. Our main customers are students who access e-resources and other services offered to them via Library website and other systems. We get nearly 1 million hits per year on Library website and around 100,000 unique visitors accessing e-resources. Our main focus in recent years has been towards e-content as there is a decrease in the usage physical content (e.g. books and print journals).
  • Digital natives - This is an interesting picture shown by Stephen Abram at M-Libraries 3 conference. Younger generation students are becoming more and more familiar with the mobile technologies Changing user expectations – more familiar with mobiles Increased number of users accessing Library/OU websites via mobile phones and small screen mobile devices
  • We developed the first version of the library website in collaboration with AU. It was a single version and basically reformatting the look and feel based on the same content. Auto-detection using Athabasca’s ADR Developed in Cold Fusion + PHP mixture About 1% of our traffic is via mobiles (without active promotion)
  • This is a more recent graph where majority of our users are accessing the website via latest touch screen phones such as iPhone, HTC and Blackberries.
  • Here is the homepage of OU Library’s new website which is due to be launched later this month and has been developed using the combination of central IT supported Drupal and PHP (with mySQL backend).
  • Same content but different layout and stylesheet …
  • Too many links + some pages will have too much content But give the option to switch between full website and mobile version
  • Mobilising is not about shrinking the page. In this example, there are too many links on the page.
  • Use only essential and relevant content Restyle Reduce options and simplify
  • RISE – Recommendations Improve Search Experience
  • MIT’s mobile web software – reusing (and customizing) their style sheets and templates Some ideas from NCSU mobile site Combination of Drupal and PHP – top develop front end WURFL for device capabilities detection mySQL – for back-end database
  • How does the student know that? And why can’t they use their institutional login to access the content?
  • Getting user feedback/requirements is important. There is no point in investing time and money in developing something they wont benefit from
  • According to ComScores 2010 report mobile internet browsing is far more popular than app use. However, the Neilsen Norman Group suggest that apps are better for regular or loyal users.
  • Other work… LOG – Learning Objects Generator tool – to facilitate users to author LO based IL activities both for desktop and in mobiles friendly manner, and deploy across multiple platform including VLE Mobile Safari - Offshoot of OU information literacy courses Safari. The mobile interface is developed using mobile ESL at AU iKnow - Information skills for the workplace
  • MIT’s Mobile web – place, events, course information, shuttle schedule etc. Molly – open source framework. Services include library search, transport timetables, podcasts, web cams, weather information, VLE link etc. MyBristol – Funded by JISC and developed by University of Bristol
  • MACON will address challenges involved in delivering quality academic content to mobile devices in a seamless and user-friendly manner. Mainly around authentication and user interface.
  • Iet tcm 5th_oct2011

    1. 1. Meeting the needs of Library users on the mobile web Hassan Sheikh and Owen Smith – The Open University Library. IET Technology Coffee Morning, 5 th October, 2011.
    2. 2. The Open University Library
    3. 3. Mobile OU Library website: Our motivation
    4. 4. Mobile OU Library website – v1 (early 2008)
    5. 5. Mobile OU Library website: v1 – top visited pages
    6. 6. Mobile OU Library website: v1 – top mobile devices accessing the website
    7. 7. The Arcadia Programme arcadia@cambridge: rethinking the role of the research library in a digital age Full report available Cambridge University Library
    8. 9. The new OU Library website
    9. 10. Revamping the current Mobile OU Library website Current mobile OU Website – single version New (under development) version – three devices model
    10. 11. Mobile OU Library development - timeline 2007 2008/09 2010/11 Oct 2011 Launch of new OU Library website (Desktop and mobile versions) Development of current OU Library website (Desktop and mobile versions) Further requirements gathering through Arcadia fellowship, by tracking users via GA and capturing user feedback through focus groups & surveys (Desktop and mobile versions) Re-development of OU Library website (Desktop and mobile versions)
    11. 12. Mobile OU Library website – v2 (In development) Three devices model (Inspired by MIT and NCSU mobile web) Low end (basic web enabled phones) High end (touch screen) Middle end (smart phones)
    12. 13. Mobile OU Library website development Three devices model categories Source: NCSU presentation at EduCause seminar in 2010 High end iPhones, Android phones, Palm Pre Large touch screens, sophisticated web capabilities Smart phones Blackberry, Nokia smartphones, Windows mobile, etc. May lack touch screen and some CSS and JavaScript capabilities. Feature and basic web phones Web-enabled flip phones Small screens, low web functionality
    13. 14. Mobile OU Library website: v2 (In development) – Offer key services <ul><li>Only offer what users want rather than mobilising everything </li></ul><ul><li>But provide option to switch between Full and mobile versions </li></ul>
    14. 15. Mobile OU Library website: v2 (In development) Key areas for mobile users <ul><li>Helpdesk hours </li></ul><ul><li>Contact us </li></ul><ul><li>About us </li></ul><ul><li>Search </li></ul><ul><li>Library News </li></ul><ul><li>Library Events </li></ul><ul><li>Help and support </li></ul>
    15. 16. What to mobilise?
    16. 17. Desktop version to small screen version Desktop version of help and support page Mobile version
    17. 18. Mobile OU Library website: v2 (In development) Help desk hours
    18. 19. Mobile OU Library website: v2 (In development) One stop search
    19. 20. Mobile OU Library website: v2 (In development) Recommendations Course(s) based recommendations Similar articles based recommendations Similar search terms based recommendations
    20. 21. Mobile OU Library website: v2 (In development) List of mobiles friendly databases
    21. 22. Mobile OU Library website: v2 (In development) Web chat
    22. 23. Mobile OU Library website development Tools and technologies
    23. 24. Challenges …
    24. 25. Too many mobile devices …
    25. 27. … but we have an app Keren Mills Articles R Us Articles R Us
    26. 28. Mobile usability/design principles
    27. 29. Mobile usability/design principles <ul><li>Know your audience and know what they’re likely to want to do on a mobile device. </li></ul><ul><li>Which phone type to design for? - Your web page is most likely to be viewed on a touch screen phone </li></ul><ul><li>Leave space around buttons and links to ensure they have a big enough “target size” (1cm x 1 cm) </li></ul><ul><li>Minimize the number of clicks and the volume of downloads </li></ul><ul><li>Save state – expect bad connectivity and ensure users will be returned to the page they were on if their connection drops temporarily – especially for forms </li></ul><ul><li>Include search </li></ul><ul><li>Reduce clicks, scrolling, and time needed to complete a task </li></ul>
    28. 30. Mobile services development - tips and recommendations …
    29. 31. Mobile services development - tips and recommendations … <ul><li>One size doesn’t fit all – develop separate mobile versions for different categories of devices </li></ul><ul><li>Collaboration – saves time </li></ul><ul><li>Re-use: Don’t reinvent the wheel – Plagiarism is OK if you are copying open source code! </li></ul><ul><li>HTML5 based web apps if there isn’t a specific need for a native app </li></ul><ul><li>Don’t just shrink the pages - but mobilize the relevant and useful content </li></ul><ul><li>Rapid and iterative development – include regular feedback from users into the development </li></ul>
    30. 32. Website or App? <ul><li>What are the characteristics of mobile apps and mobile-optimised websites? 22 July 2010. </li></ul><ul><li>W3C Mobile Web Application Best Practices. 14 December 2010. </li></ul>
    31. 34. Examples of external mobiles development work
    32. 35. JISC MACON bid … MACON – Mobilising Academic Content ONline
    33. 36. M-Libraries 4 conference 24-26 September, 2012 @ The Open University, UK.
    34. 37. Preview of new Library website features and search prototypes
    35. 38. Legacy Subjects Legacy Subjects
    36. 39. Why are we changing the subjects? <ul><li>We are moving towards the </li></ul><ul><li>The OU Qualifications Framework </li></ul><ul><li>Alignment with UCAS </li></ul><ul><li>Alignment with JACS </li></ul>
    37. 40. Is it relevant? <ul><li>Currently ICT, Information systems </li></ul><ul><li>or relevant for.... </li></ul>
    38. 41. New subjects
    39. 42. In context help
    40. 43. More in context help
    41. 44. Some unique search phrases
    42. 45. More helpful searching...
    43. 46. One stop search API
    44. 47. Questions?
    45. 48. Thank you! Hassan Sheikh ( [email_address] ) Head of Systems Development The Open University Library, United Kingdom Owen Smith ( [email_address] ) Programmer/Web developer The Open University Library, United Kingdom