[PowerPoint, (2.27 mb)]
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


[PowerPoint, (2.27 mb)]






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Talking about the future of our libraries and what path our libraries must take if they are to remain relevant in today's and tomorrow’s information environments. At this institute, we have heard about [],[], and [] and we see everyday how influences outside of the library have had an influence on our users expectations.
  • Libraries are trapped between the traditional roles of the library and the current expectations of its users.
  • User now look to other sources: Wikipedia, blogs, etc. as authorized content.
  • Library needs to be transparent – Unlike vendors, we are successful when users don’t notice what’s going on in the background. We need to do a better job not tripping over our own technology. What do I mean. Current openURL resolvers offer a good example of this. In most cases, libraries have setup their resolvers to provide users with information regarding fulltext, their catalog, additional resources…but when a user clicks on an article – they often times just want to get to the article, so we should just send them to the article. Outside technologies – Good example of this would be OpenSearch. As a protocol – you have thousands of developers, corporate backing and a simple implementation…yet libraries continue to push SRU (which itself has a very low implementation rate). On the good side, the SRU folks have made an effort to work with the OpenSearch folks to allow SRU to work with OpenSearch so it still may all work out.

[PowerPoint, (2.27 mb)] Presentation Transcript

  • 1. Breaking out of the box: libraries without walls Terry Reese [email_address] Readex Digital Institute
  • 2.
    • Libraries today are suffering from an identity crisis – trapped between the traditional roles of a library and the current expectations of its users.
  • 3. Users want….
  • 4. So long as it fits on….
  • 5. Or works with this…
  • 6. Or this…
  • 7. Or this…
  • 8. Libraries’ evolving roles
    • Library as its communities primary information provider
    • Research collections housed within the library
    User Community
  • 9. Libraries’ evolving roles
    • Library as its communities’ primary information provider
    • Library facilitates borrowing from other institutions (ILL)
    User Community
  • 10. Libraries’ evolving roles
    • Library as an information facilitator
      • Points users to ejournals
    • Splintering of library services
      • ILL, Virtual Reference, Ejournals, Digital Collections, ILS, IR, etc.
    User Community Ejournals
  • 11. Libraries’ evolving roles
    • Library one of many information providers available to their users
    User Community Google MS Live
  • 12.  
  • 13. Libraries’ evolving roles
    • Not new
      • Libraries have traditionally evolved with technology
    • But…
      • Libraries are no longer the central repositories for trusted information
  • 14. Libraries’ evolving roles
    • Evolution isn’t necessarily a bad thing
      • Underlines libraries’ past successes
      • Demonstrates a vibrant information ecosystem which libraries have traditionally cultivated
    • Library is now just a part of this ecosystem
  • 15.
    • Evolving means learning a new language and new rules without losing some of the core library values.
  • 16. Library 2.0 RSS – Really Simple Syndication
  • 17. Library 2.0 Wikis
  • 18. Library 2.0 New Programming Tools: AJAX, API
  • 19. Library 2.0 Blogs and Blogging
  • 20. Library 2.0 Commentary and Comments
  • 21. Library 2.0 Personalization and My Profiles
  • 22. Library 2.0 Podcasting and MP3 files
  • 23. Library 2.0 Streaming Media – Audio and Video
  • 24. Library 2.0 Reviews and User-Driven Ratings
  • 25. Library 2.0 Recommender Functionality
  • 26. Library 2.0 Personalized Alerts
  • 27. Library 2.0 Web Services
  • 28. Library 2.0 Instant Messaging and Virtual Reference
  • 29. Library 2.0 Folksonomies, Tagging and Tag Clouds
  • 30. Library 2.0 Photos (e.g. Flickr, Picasa)
  • 31. Library 2.0 Social Networking
  • 32. Library 2.0 Socially Driven Content
  • 33. Library 2.0 Open access, Open Source, Open Content
  • 34. Library 2.0 Social Bookmarking
  • 35. Library’s place
    • Digital library development needs to start with an understanding that:
      • The library needs to be more transparent
      • The library needs to look outside the library community for usable technologies
      • The library is no longer their user communities primary research tool of choice
  • 36. In 5 years, in my library….
    • Simple aggregation of resources will not be enough. Databases and Websites will be replaced by mechanisms that fetch information into our users’ workflows.
  • 37. In 5 years, in my library…
    • ‘Intermediate environments’ will be as important to consumers of library services as traditional end-users.
  • 38.
    • What are “intermediate environments”?
      • Think mashups
      • Think aggregations
      • Think workflow
  • 39. Examples?
  • 40. What can we do?
    • Work with partners
      • No library is large enough to solve these problems themselves. Libraries have traditionally been able to talk a good game regarding collaboration, but tend to be short on results.
  • 41. What can we do?
    • Continue to innovate
      • Libraries need to do more development. Libraries should spend less time looking at their vendors to solve solutions that should be developed within the libraries’ Open Source Community.
  • 42. What can we do?
    • Open our current systems to outside users
      • The library community expects groups like publishers, Google, etc. to provide stand access points or harvested metadata, yet we don’t build this facility into our own systems.
  • 43. IHP
    • Interoperability
      • Supporting the request and response for many different protocols:
        • SRU
        • Z39.50
        • etc.
  • 44. IHP
    • Harvestablity
      • Libraries should be building systems that allow users to harvest their metadata content.
      • Libraries need to be willing to give up some control over their metadata and be willing to see their metadata repurposed in other ways.
  • 45. IHP
    • Pluggability
      • Libraries should look to build and use systems that allow for the use of microformats.
        • COINS
        • UNAPI
  • 46.
    • Thank You