ºÝºÝߣ

Editor's Notes

1. 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).
2. 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 ¨C more familiar with mobiles Increased number of users accessing Library/OU websites via mobile phones and small screen mobile devices
3. 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)
4. 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.
5. 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).
6. Same content but different layout and stylesheet ¡­
7. Too many links + some pages will have too much content But give the option to switch between full website and mobile version
8. Mobilising is not about shrinking the page. In this example, there are too many links on the page.
9. Use only essential and relevant content Restyle Reduce options and simplify
10. RISE ¨C Recommendations Improve Search Experience
11. MIT¡¯s mobile web software ¨C reusing (and customizing) their style sheets and templates Some ideas from NCSU mobile site Combination of Drupal and PHP ¨C top develop front end WURFL for device capabilities detection mySQL ¨C for back-end database
12. How does the student know that? And why can¡¯t they use their institutional login to access the content?
13. Getting user feedback/requirements is important. There is no point in investing time and money in developing something they wont benefit from
14. 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.
15. Other work¡­ LOG ¨C Learning Objects Generator tool ¨C 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
16. MIT¡¯s Mobile web ¨C place, events, course information, shuttle schedule etc. Molly ¨C open source framework. Services include library search, transport timetables, podcasts, web cams, weather information, VLE link etc. MyBristol ¨C Funded by JISC and developed by University of Bristol
17. 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.