1. Wednesday, February 02, 2011 1 Event Name and Venue Pilot implementation of campusM David Clark
2. Wednesday, February 02, 2011 Event Name and Venue 2 Pilot of CampusM Survey of mobile device usage Survey results campusM Pilot Mobile applications we developed Technologies to monitor Recommendations
3. Mobile devices survey What we did For two weeks during March 2010 we published a survey through the portal to all staff and students on all campuses. The objectives of the survey were to establish what appetite staff and students had for using mobile devices (Smartphones / standard phones / eBook readers), what they used and how they used them. We had over 800 responses from all campus’s
4. Some of the questions we asked… Do you have a mobile device (eg phone, notebook, e-book reader, Smartphone)? What features are currently available on your mobile devices? How often would you use each of these features? If necessary, would you be prepared to upgrade your device to access the extra services? If you have used e-books, what do you like about them? What do you dislike about them Would you be happy to be contacted about future research in this area? What category best describes you? Student, Staff (not teaching or research related), Staff (Teaching/Research) If applicable - Please state your level/category of study (egpostgrad taught, postgrad research, undergraduate) What nationality are you? (Optional) The results.........
7. Wednesday, February 02, 2011 Event Name and Venue 7 Pilot of CampusM Main Deliverables Install & configure Ombiel’s campusM software Pilot the software to approximately 300 students (PG & UG) * some staff licenses are available for testing Estimate the cost of rolling this out live to all are UK and international campuses. To evaluate support requirements in the live environment Provide some basic branding for the application Investigate potential uses for Prospective Students & PG/UG Open Days Make further recommendations for use in supporting our delivery of research & learning.
8. Wednesday, February 02, 2011 Event Name and Venue 8 Pilot of CampusM Applications to be delivered :- Campus ‘push’ Alerts Campus Maps Friend Locator News/Events UoN Pocket guide Library catalog search Course timetable Financial Accounts
12. Technologies we should monitor ‘Bluetooth 3 & 4 will support faster data transmission’ – devices that can talk to each other The mobile web: 2011, over 85% of mobiles will include some form of browser. The trend towards larger screens will further enhance the usability of the mobile web. More people will encourage greater numbers of people to access conventional websites on mobile devices’ ‘Mobile platforms will become more diverse’. Can we choose a standard to support as many as possible? Application ‘stores’: App stores will be the primary way to deliver applications to Smartphones. Application stores are becoming the fundamental way that users use Smartphones – they can generate a lot of money Enhanced Location Awareness: GPS will be the primary, but not the only means, of establishing handset location. ‘By the end of 2011, over 75% of devices shipped in mature markets will include GPS’ Local privacy regulations, ensure that applications that expose location are ‘opt in’ – there will be concerns and risks which have to be investigated Touchscreens: are emerging as the dominant user interface for large screen handsets – 60% of handsets will be touch screen by 2011 in Western Europe and North America
13. Recommendations (1) Libraries should investigate: The use of texting alerting services created by the library management system – alerts / notifications /facts / updates/ book renewal / fines /general library service information/audio tours for new students * 55% of users at Cambridge were in favour of being able to access the library catalogue from a mobile phone. Other recommendations from users include providing information on opening hours, location maps, contact information, library catalog, electronic books, study aids, tutorials, training sessions Providing staff/students with an mobile interface to some of the data in our library system / reference / searches / loans Develop a standardised developer framework Develop for as many mobile devices – don’t commit to one technology Don’t provide information on mobile devices that cant be found some where else – this would cause problems for staff/ students who don’t own a capable phone
14. Recommendations (2) We already have access to a considerable volume of material through a number of sources. (600,000 books in our collections that are already available electronically) It would be useful to continue to work with publishers in this area It would be worthwhile revisiting this area on a regular (probably annual) basis to examine and review progress in this area and recommend further initiatives in this area Continue to monitor development of Digital Rights Management, eBook reader formats and hardware Continue to trial the devices in small groups of staff and students
15. Recommendations (3) Identify content for Student channels Identify content for Staff channels The Web Strategy should include a mobile devices strategy Continue to make mobile content available through services such as iTunes U and CampusM, but ensure that it is not limited to, or targeted at one specific device (such as the iPhone) as this would severely limit the take up and use of the services Investigate integrating with the VLE Move towards ensuring Web-based content is available in format suitable for mobile devices, as well as moving towards a policy of making data available via web interfaces as far as possible
16. What next? Comprehensive mobile strategyInfrastructure – roll outArchitectureInvestigate the use of mobile devices in Learning and Teaching