1. 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

2. slides adapted from a presentation by Nicole Hennig Web Manager and Usability Specialist MIT 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 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
user feedback
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

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
the beta has received positive user feedback
“This is a wikked cool tool for researching, and could be very useful for working on reading lists.  I've tested it out and found it really user-friendly.”
it has been in beta for at least one semester
Fall 2006
it has been demonstrated that our community is using it
MIT’s LibX has highest number of downloads of all libraries using LibX

11. LibX has “graduated” tech support
documentation, training, and workflow are in place
help pages in place; “Ask Us” staff knows how to answer basic questions and refer more complex ones
if it's provided and supported outside of MIT, it's from a trusted and reliable source
Virginia Tech University Libraries and Department of Computer Science

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. libraries.mit.edu/betas
questions?
libraries.mit.edu/betas