1 / 26

Library Mobile App Student Competition

Library Mobile App Student Competition . Orientation Session 1. Library Mobile App Student Competition .

mick
Download Presentation

Library Mobile App Student Competition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Library Mobile App Student Competition Orientation Session 1

  2. Library Mobile App Student Competition This competition is a key part of the grant “The Student/Library Collaborative:  Toward Transformative Mobile Library Service” that is funded by the Institute of Museum and Library Services (IMLS).  The Library Innovation Fund provides additional support for the competition.

  3. Agenda • Team Meet and Greet • Competition Introductions – Lori Mestre, Head, Undergraduate Library • Library Mobile App Development – Jim Hahn, Associate Professor, Undergraduate Library • Competition Goals and timeline – David Ward, Associate Professor, Undergraduate Library • Q and A from student teams • Next orientation session is in on Saturday, Jan 26, from 1 to 4 p.m.

  4. Team Meet and Greet • Icebreaker Topic: What is the coolest App you have used? • Team Assignments for those not yet on a team • Choose Team Names • Refreshments

  5. Introductions – Lori Mestre, Head, Undergraduate Library, and Associate Professor • Document and share best practices for working with student design teams • Two year National • Leadership Grant (IMLS)

  6. IncreaseStudent Input Create Connections Identify Transferrable Best Practices

  7. Library Mobile App Development – Jim Hahn, Associate Professor, Undergraduate Library • We don’t want to redo already existing services. • We need your ideas for new apps and new services to develop.

  8. What’s been done…. • We have • Book search of the online catalog • Article search of EBSCO databases • Reserves • Maps of the stacks to your location • A barcode scanner • A feed of technology availability

  9. Library Book Search Result

  10. Search Bar for Library Catalog

  11. We have these parts in the works… • Citation Generator • Calendar and Events Feed • Augmented Reality and Optical Character Recognition features • Fines and Library Account Login • Facebook and a Favorites option

  12. Library Reserves Module…

  13. We haven’t quite figured location yet.. • We’d like ideas around the areas of places people may be in and need library or campus information. • Or library or campus location specific apps • Or other location type services, like while you’re on a bus…

  14. How we did those… • We have some connectors in place that allow us to plug library data into apps pretty easily. • You don’t have to be familiar with this, but you should know its not a problem to pull library data into any parts of mobile apps, like all types of technology, all our group rooms that are available, and so on…

  15. Data pipeline…

  16. Questions on previous work?

  17. Competition Goals and Timeline – David Ward, Associate Professor, Undergraduate Library • Identify student library–related needs in the mobile environment • Identify related problems that a mobile application could solve • Develop a design outline and formal proposal for a mobile application • Emphasis on location-based needs • Functioning apps are NOT required – just designs

  18. Example Mobile App Concept Drawing

  19. Example with a more professional look

  20. Example that explains functions

  21. Example Showing Screen Interaction

  22. Orientation Session 2 is this Saturday, Jan 26, from 1 to 4 p.m. • Meet at Room 291, UGL at 1 p.m. • Please arrive a few minutes early • Dress warm, this will be a walking tour of campus • At least 50% of each team must participate • Teams will visit common undergrad locations, and brainstorm possible needs for a library mobile app • Be prepared to take notes • At the end of the tour, teams will turn in a one-paragraph summary of their top observations

  23. Competition Goals and Timeline – David Ward, Associate Professor, Undergraduate Library • Presentation Reviews • Feb 11th, 13th, and 14th 6-9pm • Each team will sign up for one time slot • Teams present an overview of their app • Competition organizers review to make sure it meets competition guidelines • Teams can ask questions

  24. Competition Goals and Timeline – David Ward, Associate Professor, Undergraduate Library Presentation Review Session Overview Document • Name of App • “Pitch” statement – 2-3 sentence overview describing app and how it will function • Short (1-2 sentence) biographical statement for each participant, stating name, major/college, and role on team. • Problem the app is designed to solve, including evidence for the need for the app • Audience for the app • Mock-up of the App in action, including sketches or other visual representations of the app in use during a typical interaction • Example use cases for the app • How and why the app will improve student access to library collections, services, and/or facilities.

  25. Competition Goals and Timeline – David Ward, Associate Professor, Undergraduate Library Final Judging • Thursday, Feb 21, 6-9pm • ACES Heritage Room (First Floor) • All team members must be present • Teams cannot be in presentation room until they present

  26. Competition Goals and Timeline – David Ward, Associate Professor, Undergraduate Library Judging Criteria • Clearly identified connection to library services, collections, and facilities • User experience/design layout; • Originality/creativity; • Clear identification/explanation of the need for the app and problem(s) it addresses; • Evidence that the app addresses student interests and needs; • Integration of identified library/3rd party data sources

More Related