1. Creating tools for the mobile campus
David Woodbury | October 14, 2010

2. NC State University Libraries
We serve the largest higher education institution in the state
31,000 students & 8,000 faculty members
Large focus on science, technology, engineering & mathematics
Our main library is the busiest building on campus
Up to 16,000 visitors a day
Resources get maxed out

3. WHY MOBILE?
“People expect to be able to work, learn, and study whenever and wherever they want to.”

4. Why mobile?

5. NC state Mobile Web

6. Our mobile services
MobiLIB (2007)

7. Our mobile services
Texting from the catalog

8. Our mobile services
Text and Voice Reference Services

9. Our mobile services
NCSU Libraries Mobile
m.lib.ncsu.edu

10. Our mobile services
WolfWalk

11. Project Team Jason Casden, Digital Technologies Development Librarian
Developer
David Woodbury, NCSU Libraries Fellow
Project manager
Markus Wust, Digital Collections and Preservation Librarian
Developer & co-creator of MobiLIB

12. How we got started
Three months from planning to launch
September: Project planning, site wireframes (one project manager)
October: Development and testing (two developers)
November: Formal launch & promotion
December: Main website redirect

13. Iterative development
Enhancements added by other developers
Bug fixes as needed for new devices
new
new
new
new

14. Ncsu Libraries mobile m.lib.ncsu.edu
Direct access to dynamic library services
Device detection to deliver 3 tiers of content (based on MIT Mobile Web framework)

16. Locations and Hours

17. Locations and Hours

18. Locations and Hours

20. Catalog Search

21. Catalog search

22. Catalog Search

23. Catalog Search

25. Computer Availability

26. Computer Availability

28. Room Reservations

29. Room Reservations

30. Room Reservations

32. Webcams

33. Webcams

34. Our mantra
Reduce
Reuse
Keep the user in mind

35. REDUCE 

36. REDUCE

37. Reduce

38. REUSE
Mobile tools use existing web applications

39. REUSE

40. Reuse

41. REUSE
WolfWalk

42. Keep the user in mind Our site works better with fewer options
Sometimes mobile context means different or special data
Say no to projects missing a mobile use case

43. Native vs web-based Charging for it Creating a game Using cameras
Using accelerometers
Accessing the filesystems
Offline users
For publicity and discoverability

44. Tech tools NCSU Libraries Mobile MIT Mobile Web Open Source Project
XHTML 1.0 transitional
CSS
non-essential JavaScript and AJAX
MIT Mobile Web Open Source Project
Leaned on pre-existing web services (JSON, RSS)
Targeted higher-end devices

45. Testing
CC BY-SA 2.0:

46. Build it and they will come?

47. What services are used?
Unique visits to services

48. What devices are used?

49. Where we go from here Add patron account information access
Add additional reservation capabilities
Promotion!
SMS
Integrate into instruction

50. Where we go from here Exploring interior location based information
QR code test
Enhancing Special Collections exhibits

52. Where we go from here Collaborate with other campus units
Integrate user experience across channels (mobile, web, e-boards)
Continue to steal from others and share back!

53. David Woodbury | david_woodbury@ncsu.edu
THANK YOU
David Woodbury |