Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Web 2.0 in Libraries: Theory and Practice

•
•
Meredith Farkas
Meredith Farkas

The document discusses the evolution of the web from Web 1.0 to Web 2.0 and the concept of Library 2.0. It describes how Web 2.0 enables user participation and collaboration through social software. Library 2.0 aims to harness collective intelligence and user participation by implementing Web 2.0 technologies and principles in libraries, such as wikis, user tagging, and user-driven services. The document provides examples of libraries that have implemented Library 2.0 ideas and discusses practical considerations for libraries looking to adopt Web 2.0 approaches.

Related slideshows

Library 2.0
Library 2.0Library 2.0
Library 2.0
 
Web 2.0
Web 2.0Web 2.0
Web 2.0
 
Library2 Presentation
Library2 PresentationLibrary2 Presentation
Library2 Presentation
 
1 of 60
Web 2.0 in Libraries: Theory and Practice Meredith Farkas SLA Click University Live! January 10, 2007
Presenter Meredith Farkas Distance Learning Librarian at Norwich University (VT). Author - Social Software in Libraries . Columnist – “Technology in Practice” column in American Libraries . Blogger - Information Wants to be Free and TechEssence . Wiki manager - Library Success , ALA 2005 and 2006 , etc.
What we will explore How the Web has changed since its birth in the early 1990s. How the idea of Web 2.0 developed. Characteristics of Web 2.0 How the idea of Library 2.0 developed. Some examples of libraries implementing 2.0 ideas and technologies
The Web of 1994 (Web 1.0) Democratized access to information Most people were not able to put content on the Web. Websites were largely one-way communications vehicles. People still primarily got online information from major companies. Some “social software” Forums and electronic mailing lists
Web of 2007 (Web 2.0) Democratized participation. Anyone can add content. Many Websites allow commenting, participation, personalization, etc. People have more options when choosing information providers. Lots of social software allows people to build community from the bottom-up and collaborate in real time.
Birth of Web 2.0 as a concept Tim O’Reilly (of the books and conferences) was meeting with folks from MediaLive International who put on conferences and trade shows. Looking for a way to define the post-dotcom bust era (marketing gimmick). All of this was going on before Tim O’Reilly coined the term, but he gave it a name and gave people an idea to rally around.
Early definition of Web 2.0
 
Web 2.0 – Ways to Define Web architecture AJAX Web as platform API Mashups Human aspects Web 2.0 is made of people Network effects Wisdom of crowds Personalization Community
Web 2.0 Architecture
Web as Platform Web applications replace desktop applications.
API API=Application Programming Interface Exposes a set of functions that make up the application and can be used in the creation of other applications. Allows a developer to access the functions of another application in their own application so that they don’t need to build the functionality from scratch. Examples: Amazon, Google, eBay
Mashups Involves combining (or mashing up) two separate applications, or an application and data, to create an entirely new one. Usually done through APIs, but sometimes screenscraping must be done. Screenscraping – taking data directly from a Website.
 
 
RSS RSS is format for syndicating content on the Web. Based on XML Enables you to view content from different sites on a single page. Many Web sites have RSS feeds these days if they have information that is updated regularly (examples: CNN , NY Times , Burlington Free Press ). You can view RSS-enabled content on another Website, in an aggregator or via e-mail.
Web 2.0 Design Strategy Lightweight architecture Rich, interactive and agile interfaces AJAX – Asynchronous JavaScript and XML. Allows pages to interact with the server without having to refresh Makes Web applications as responsive as desktop applications Perpetual beta allows for continuous improvements.
The Human Aspect
 
Harnessing the Collective Intelligence There is a lot that can be learned from the aggregate knowledge and behavior of people online. Ratings systems Knowledgebases Folksonomy
Would you rather get advice from a travel writer or millions of travelers like you?
Wikipedia – The New Peer Review?
Making Sense of the Web – 1.0
Making sense of the Web – 2.0
 
Network Effect The more people who are using a specific tool, the more useful it becomes. More recommendations = better recommendations (normalize the outliers). More reviewers of Wikipedia = more oversight. More people tagging Websites, more accuracy in tagging.
Self-Expression
Egalitarianism Bloggers are revealing political corruption before mainstream media More opportunities to showcase your talent Bloggers getting book deals YouTube video creators are becoming celebrities Podcasters getting contracts with music industry
Personalization
 
Transparency If a technology is bad, people will quickly find out about it (blogs, ratings, etc.) Companies trying to connect with users in a more personal way. Blogs (example: GM’s Fastlane Blog) Marketing via social networking sites
Web 2.0 Backlash “ The Web is real. The Semantic Web is an idea and Web 2.0 is a marketing concept used by venture capitalists and conference promoters to try to call another bubble into existence.” -”Old Hype, New Hype.” Scripting News “ Over the last couple of months I've noticed an increasing sense of unease in the venture community about the trend in Web 2.0 company creation and financing events. While no one is officially willing to peg it Bubble 2.0 for fear of missing the next great opportunity, I've been having lots of conversations with venture investors about this nagging feeling that we've been here before.” -“Built To Be Bought (Bubble 2.0)” Venture Blog “ Well, Web 2.0 is bunk. Not that the elements of this rebirth aren’t there… It’s just that they cannot be classified under a common umbrella. They are forward lurches of various standards and technologies, some compatible, some not. Some revolutionary, some evolutionary, some impractical. Some are collaborative, others are highly competitive with each other.” -”Web 2.0? It doesn’t exist.” IP, Telephony, VOIP, Broadband
Downsides So much content… few efficient ways to search it The crowd isn’t always right Trusting companies with your content Who owns your content? Privacy issues Copyright issues
Library 2.0 Michael Casey of the blog Library Crunch coined the term in Fall 2005. Popularized by popular bloggers and speakers in librarianship. Book on Library 2.0 coming out in Spring 2007. Controversial topic.
What is Library 2.0? User-driven change Harnessing the long tail to provide services to people who don’t use the library Harnessing the collective intelligence More usable and transparent library systems (built on Web 2.0 ideas)
Library 2.0 Principles (by Paul Miller and Ken Chad of Talis) The library is everywhere Available at the point of need Go where our users are The library has no barriers No barriers between user and information The library invites participation Blogs, wikis, tagging and commenting in the catalog, etc. The library uses flexible, best-of-breed systems ILS made of small pieces loosely joined. Modular, interoperable Web services.
What makes a library service 2.0? According to Michael Casey and Laura Savastinuk (authors of the forthcoming book on Library 2.0): “ Any service, physical or virtual, that successfully reaches users, is evaluated frequently, and makes use of customer input is a Library 2.0 service. Even older, traditional services can be Library 2.0 is criteria are met. Similarly, being new is not enough to make a service Library 2.0.”
 
Library 2.0 in the Real World User driven change – survey your users, start an Advisory Board, talk to people in the community. Examine your policies (do they enable or alienate your users?) Harnessing the long tail – Interlibrary Loan services, Netflix-type services, downloadable media. Harnessing the collective intelligence – subject guide wiki, user comments in the catalog, etc.
Library 2.0 in the Real World (cont’d) Better library systems – OPACs that work more like Amazon and Google. The library is everywhere – library services in MySpace, courseware, company Intranet. Web presence designed to meet users’ needs 24/7 The library has no barriers – library resources are easier to find (be it through link resolvers, federated search, etc.) Perpetual beta – library is always re-examining and improving policies and services.
Criticisms of Library 2.0 These ideas aren’t new Too many ideas that don’t fit well under one umbrella The label may alienate We should focus more on concrete change than on labels Is Library 2.0 just for rich libraries or libraries that employ coders? Privacy concerns
Libraries Going 2.0
Ann Arbor District Library
 
 
Hennepin County Public Library
North Carolina State University Libraries Catalog
 
 
University of Wisconsin-Madison Ebling Library for the Health Sciences
Palos Verdes Library 40 Families Project
 
Washington State Library
 
 
Jenkins Law Library
Practical Considerations Find out what your population needs and wants from the library. Ask people who don’t use the library what they’d like to see. Examine current services and policies – are they meeting the needs of your population? Do a usability study of your physical and online “space.” Think about “experience” Fight the urge to say/think “but we’ve always done it this way.”
Practical Considerations (cont’d) How can you provide library services where your patrons are and at their point of need? Find out what Web 2.0 tools your patrons may already be using. Look at what services other libraries of your type are providing. No one-size-fits-all approach – your population is unique. Don’t try to “keep up with the Joneses.”
Coming Up in Part 2 The Tools of Web 2.0 RSS Wikis Social Bookmarking Custom Search Instant Messaging How these are being used in libraries Strategies for implementing Web 2.0 tools in libraries
Any Questions? Meredith Farkas [email_address] http://meredith.wolfwater.com/wordpress/

More Related Content

Web 2.0 in Libraries: Theory and Practice

  • 1. Web 2.0 in Libraries: Theory and Practice Meredith Farkas SLA Click University Live! January 10, 2007
  • 2. Presenter Meredith Farkas Distance Learning Librarian at Norwich University (VT). Author - Social Software in Libraries . Columnist – “Technology in Practice” column in American Libraries . Blogger - Information Wants to be Free and TechEssence . Wiki manager - Library Success , ALA 2005 and 2006 , etc.
  • 3. What we will explore How the Web has changed since its birth in the early 1990s. How the idea of Web 2.0 developed. Characteristics of Web 2.0 How the idea of Library 2.0 developed. Some examples of libraries implementing 2.0 ideas and technologies
  • 4. The Web of 1994 (Web 1.0) Democratized access to information Most people were not able to put content on the Web. Websites were largely one-way communications vehicles. People still primarily got online information from major companies. Some “social software” Forums and electronic mailing lists
  • 5. Web of 2007 (Web 2.0) Democratized participation. Anyone can add content. Many Websites allow commenting, participation, personalization, etc. People have more options when choosing information providers. Lots of social software allows people to build community from the bottom-up and collaborate in real time.
  • 6. Birth of Web 2.0 as a concept Tim O’Reilly (of the books and conferences) was meeting with folks from MediaLive International who put on conferences and trade shows. Looking for a way to define the post-dotcom bust era (marketing gimmick). All of this was going on before Tim O’Reilly coined the term, but he gave it a name and gave people an idea to rally around.
  • 8.  
  • 9. Web 2.0 – Ways to Define Web architecture AJAX Web as platform API Mashups Human aspects Web 2.0 is made of people Network effects Wisdom of crowds Personalization Community
  • 11. Web as Platform Web applications replace desktop applications.
  • 12. API API=Application Programming Interface Exposes a set of functions that make up the application and can be used in the creation of other applications. Allows a developer to access the functions of another application in their own application so that they don’t need to build the functionality from scratch. Examples: Amazon, Google, eBay
  • 13. Mashups Involves combining (or mashing up) two separate applications, or an application and data, to create an entirely new one. Usually done through APIs, but sometimes screenscraping must be done. Screenscraping – taking data directly from a Website.
  • 14.  
  • 15.  
  • 16. RSS RSS is format for syndicating content on the Web. Based on XML Enables you to view content from different sites on a single page. Many Web sites have RSS feeds these days if they have information that is updated regularly (examples: CNN , NY Times , Burlington Free Press ). You can view RSS-enabled content on another Website, in an aggregator or via e-mail.
  • 17. Web 2.0 Design Strategy Lightweight architecture Rich, interactive and agile interfaces AJAX – Asynchronous JavaScript and XML. Allows pages to interact with the server without having to refresh Makes Web applications as responsive as desktop applications Perpetual beta allows for continuous improvements.
  • 19.  
  • 20. Harnessing the Collective Intelligence There is a lot that can be learned from the aggregate knowledge and behavior of people online. Ratings systems Knowledgebases Folksonomy
  • 21. Would you rather get advice from a travel writer or millions of travelers like you?
  • 22. Wikipedia – The New Peer Review?
  • 23. Making Sense of the Web – 1.0
  • 24. Making sense of the Web – 2.0
  • 25.  
  • 26. Network Effect The more people who are using a specific tool, the more useful it becomes. More recommendations = better recommendations (normalize the outliers). More reviewers of Wikipedia = more oversight. More people tagging Websites, more accuracy in tagging.
  • 28. Egalitarianism Bloggers are revealing political corruption before mainstream media More opportunities to showcase your talent Bloggers getting book deals YouTube video creators are becoming celebrities Podcasters getting contracts with music industry
  • 30.  
  • 31. Transparency If a technology is bad, people will quickly find out about it (blogs, ratings, etc.) Companies trying to connect with users in a more personal way. Blogs (example: GM’s Fastlane Blog) Marketing via social networking sites
  • 32. Web 2.0 Backlash “ The Web is real. The Semantic Web is an idea and Web 2.0 is a marketing concept used by venture capitalists and conference promoters to try to call another bubble into existence.” -”Old Hype, New Hype.” Scripting News “ Over the last couple of months I've noticed an increasing sense of unease in the venture community about the trend in Web 2.0 company creation and financing events. While no one is officially willing to peg it Bubble 2.0 for fear of missing the next great opportunity, I've been having lots of conversations with venture investors about this nagging feeling that we've been here before.” -“Built To Be Bought (Bubble 2.0)” Venture Blog “ Well, Web 2.0 is bunk. Not that the elements of this rebirth aren’t there… It’s just that they cannot be classified under a common umbrella. They are forward lurches of various standards and technologies, some compatible, some not. Some revolutionary, some evolutionary, some impractical. Some are collaborative, others are highly competitive with each other.” -”Web 2.0? It doesn’t exist.” IP, Telephony, VOIP, Broadband
  • 33. Downsides So much content… few efficient ways to search it The crowd isn’t always right Trusting companies with your content Who owns your content? Privacy issues Copyright issues
  • 34. Library 2.0 Michael Casey of the blog Library Crunch coined the term in Fall 2005. Popularized by popular bloggers and speakers in librarianship. Book on Library 2.0 coming out in Spring 2007. Controversial topic.
  • 35. What is Library 2.0? User-driven change Harnessing the long tail to provide services to people who don’t use the library Harnessing the collective intelligence More usable and transparent library systems (built on Web 2.0 ideas)
  • 36. Library 2.0 Principles (by Paul Miller and Ken Chad of Talis) The library is everywhere Available at the point of need Go where our users are The library has no barriers No barriers between user and information The library invites participation Blogs, wikis, tagging and commenting in the catalog, etc. The library uses flexible, best-of-breed systems ILS made of small pieces loosely joined. Modular, interoperable Web services.
  • 37. What makes a library service 2.0? According to Michael Casey and Laura Savastinuk (authors of the forthcoming book on Library 2.0): “ Any service, physical or virtual, that successfully reaches users, is evaluated frequently, and makes use of customer input is a Library 2.0 service. Even older, traditional services can be Library 2.0 is criteria are met. Similarly, being new is not enough to make a service Library 2.0.”
  • 38.  
  • 39. Library 2.0 in the Real World User driven change – survey your users, start an Advisory Board, talk to people in the community. Examine your policies (do they enable or alienate your users?) Harnessing the long tail – Interlibrary Loan services, Netflix-type services, downloadable media. Harnessing the collective intelligence – subject guide wiki, user comments in the catalog, etc.
  • 40. Library 2.0 in the Real World (cont’d) Better library systems – OPACs that work more like Amazon and Google. The library is everywhere – library services in MySpace, courseware, company Intranet. Web presence designed to meet users’ needs 24/7 The library has no barriers – library resources are easier to find (be it through link resolvers, federated search, etc.) Perpetual beta – library is always re-examining and improving policies and services.
  • 41. Criticisms of Library 2.0 These ideas aren’t new Too many ideas that don’t fit well under one umbrella The label may alienate We should focus more on concrete change than on labels Is Library 2.0 just for rich libraries or libraries that employ coders? Privacy concerns
  • 44.  
  • 45.  
  • 47. North Carolina State University Libraries Catalog
  • 48.  
  • 49.  
  • 50. University of Wisconsin-Madison Ebling Library for the Health Sciences
  • 51. Palos Verdes Library 40 Families Project
  • 52.  
  • 54.  
  • 55.  
  • 57. Practical Considerations Find out what your population needs and wants from the library. Ask people who don’t use the library what they’d like to see. Examine current services and policies – are they meeting the needs of your population? Do a usability study of your physical and online “space.” Think about “experience” Fight the urge to say/think “but we’ve always done it this way.”
  • 58. Practical Considerations (cont’d) How can you provide library services where your patrons are and at their point of need? Find out what Web 2.0 tools your patrons may already be using. Look at what services other libraries of your type are providing. No one-size-fits-all approach – your population is unique. Don’t try to “keep up with the Joneses.”
  • 59. Coming Up in Part 2 The Tools of Web 2.0 RSS Wikis Social Bookmarking Custom Search Instant Messaging How these are being used in libraries Strategies for implementing Web 2.0 tools in libraries
  • 60. Any Questions? Meredith Farkas [email_address] http://meredith.wolfwater.com/wordpress/