1 / 16

library 2.0 [beta] implementing new technologies in libraries using the Google Labs method

library 2.0 [beta] implementing new technologies in libraries using the Google Labs method. Darcy Duke Engineering Librarian for Technology-Based Services MIT Libraries ASEE 25 June 2007. slides adapted from a presentation by Nicole Hennig Web Manager and Usability Specialist MIT Libraries.

neviah
Download Presentation

library 2.0 [beta] implementing new technologies in libraries using the Google Labs method

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 2.0 [beta]implementing new technologies in libraries using the Google Labs method Darcy DukeEngineering Librarian for Technology-Based ServicesMIT Libraries ASEE 25 June 2007

  2. slides adapted from a presentation byNicole HennigWeb Manager and Usability SpecialistMIT Libraries

  3. outline • why we developed the “betas” concept • examples of betas • moving from beta to supported tool • questions

  4. why? • demand! engineering students are on the cutting edge of new technologies • needed a way to quickly experiment with web 2.0 technologies • needed a structured process that allowed staff throughout the libraries to experiment

  5. labs.google.com

  6. libraries.mit.edu/betas

  7. criteria for moving out of beta • the beta has received positive user feedback • it has been demonstrated that our community is using it • it has been in beta for at least one semester user feedback

  8. criteria for moving out of beta tech support • we’ve made a commitment to support it either centrally or locally with tested technologies that our staff is trained to support • if it's provided and supported outside of MIT, it's from a trusted and reliable source • documentation, training, and workflow is in place

  9. LibX adds our search to the browser toolbar libraries.mit.edu/libx

  10. LibX has “graduated” user feedback

  11. LibX has “graduated” tech support

  12. key advantages • provides a way to get experience with technologies or features that we are still learning about before committing to supporting a new service • allows us to find out what works for our users and get quick feedback • encourages staff creativity and experimentation

  13. other advantages • provides a place where the MIT community can contribute tools or hacks (in the MIT tradition of "hacks") • creates a special way to market new services - creates “buzz” before new services are live

  14. learning from failure • not all betas will "graduate“ • they can still be useful to us as something to learn from • aspects of a particular beta service may survive in other tools

  15. future betas • podcasts and screencasts • next version of Vera (database/journal lookup tool) that will include metasearch features • iGoogle homepage gadget for searching catalog

  16. questions? libraries.mit.edu/betas

More Related