Web 2.0 and Library 2.0 A Brief Overview

can be considered an “attitude, not a technology” (O’Reilly, 2005) Web 2.0 - Definitions “web-as-platform,” “perpetual beta,” and “architecture of participation,” can be considered an “attitude, not a technology” (O’Reilly, 2005)

Library 2.0 - Definitions “The heart of Library 2.0 is user-centered change. It is a model for library service that encourages constant and purposeful change, inviting user participation in the creation of both the physical and the virtual services they want, supported by consistently evaluating services. It also attempts to reach new users and better serve current ones through improved customer-driven offerings. Each component by itself is a step toward better serving our users; however, it is through the combined implementation of all of these that we can reach Library 2.0.” (Casey and Savastinuk, 2006).

Web 1.0 – Static Web 2.0 – Participatory, evolving

Some Types of technologies involved Blogs – Postings by creator(s), comments by visitors RSS feeds – a means of publishing frequently updated content so that visitors can subscribe, used for blogs, podcasts, etc. Wikis – Websites created by anyone with editing privileges Social Bookmarking – sites enabling users to save places they’ve visited on the web and to “tag” them for easy retrieval. Users can also search for items tagged by others in order to find relevant materials

Some Types of technologies involved Social Networking – Sites where you create a profile for yourself and communicate with friends and colleagues Media Sharing – Sites where you can upload and share audio-visual content The common thread is that these are: Available online from almost anywhere Easy to get started using with minimal tech skills Encourage participation and creation/editing of content

Web 2.0 - Design Patterns The Long Tail – “narrow niches make up the bulk of the internet..” We can appeal to those interested in our collections, we don’t have to worry about attracting everyone. Data is the Next Intel Inside – “seek to own a unique, hard-to-recreate source of data” In many cases we’ve already done this with our collections. No-one else has these materials. Users Add Value – “users add their own data to that which you provide” It takes some bravery, but allow users to comment on or tag our online collections. They may know something about an item that we don’t. Network Effects by Default – “Set … defaults for aggregating user data as a side-effect of their use of the application.” This may be difficult to achieve except in cases where users have to log-in to use our sites, but it’s something to keep in mind where feasible.

Web 2.0 - Design Patterns Some Rights Reserved. – “Design for “hackability” and “remixability.” To the greatest extent possible, let users manipulate, download, re-use your materials. Sometimes this is impossible due to copyright or privacy restrictions, but otherwise, open it up! Investigate Creative Commons licenses. The Perpetual Beta – “add [new features] on a regular basis” Don’t feel that you have to include everything in it’s most perfect form just to get started. Start small and gradually build up your new online offerings, with as much user feedback as possible. Cooperate, Don't Control – “Offer web services interfaces and content syndication, and re-use the data services of others.” Allow people to subscribe to updates via RSS, and to the extent possible, allow them to write programs that access your data/collections automatically for re-purposing in another context. Software Above the Level of a Single Device – “Design your application from the get-go to integrate services across handheld devices, pcs, and internet servers. Beyond my current skill level, and I can’t afford the technology, but imagine how great it would be for users to be able to access your collections while they’re waiting for the bus, etc.

Questions?