Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Library 2.0


Published on

Published in: Technology, Education
  • Be the first to comment

Library 2.0

  1. 1. Catalog 2.0 Karen Coyle
  2. 2. Timeline 1990 Exchange of data between libraries 2000 Use of the web to interact with users 2010 Exchange of library data with Web services 2020 Library catalogs are no longer a destination but an integral part of the information space …
  3. 3. The isolation <ul><li>Libraries only connect to other libraries </li></ul><ul><li>No one outside of libraries uses our bibliographic data </li></ul><ul><li>There is no direct connection between the data in library catalogs and bibliographic data found elsewhere </li></ul><ul><li>It is difficult for libraries to interact with Web services </li></ul>
  4. 4. The user begins with a search on Google Books…
  5. 5. … and is informed that the local public library has the book.
  6. 6. The library catalog can also link out to other resources….
  7. 7. … such as reviews.
  8. 8. Cataloging <ul><li>AACR1/2 – a manual standard, from 1967 </li></ul><ul><li>MARC21 – one possible way to codify AACR in a machine-readable form; a separate standard </li></ul><ul><li>FRBR – Functional Requirements for Bibliographic Records – a functional standard – 1998 </li></ul><ul><li>AACR3  RDA “Resource Description and Access” – in development as a manual standard - 2004 </li></ul><ul><li>RDA in RDF – an agreement to create a rigorous, machine-readable bibliographic standard </li></ul>
  9. 9. Functional Requirements for Bibliographic Records (FRBR) FRBR provides a basic structure for bibliographic description.
  10. 10. Creators/producers
  11. 11. Topics
  12. 12. RDA is a textual standard
  13. 13. The resulting cataloging is similar to that created for card catalogs
  14. 14. RDA includes some lists of terms that should not be part of the cataloging rules themselves. They need to be able to be used outside of RDA and they need to be able to grow.
  15. 15. These same terms could be expressed in a machine-readable web format.
  16. 16. Information can be given about each term, with broader and narrower concepts.
  17. 17. While a human will see an eye-readable display, a machine accessing that same term will be given the data in a format that it can use programmatically.
  18. 18. The context within the vocabulary is included
  19. 19. New terms can be added at any time, without requiring a change to the standard itself.
  20. 20. An entry for a term can include definitions, synonyms, or any other information included in the design of the vocabulary software.
  21. 21. All of this information about the term becomes available to programs, and might be used to aid input or to inform catalog users.
  22. 22. Dublin Core + FRBR + RDF The Dublin Core community is already experimenting with FRBR, showing how a shared view of the deep structure of bibliographic data can lead to compatibility between standards.
  23. 24. Article 1. Smith, John. “Use of Dublin core with FRBR” New York, London, 2007 Library Catalog <bb:description> <bb:statement <bb:propertyURI=“bibPerson” bb:propertyURI=“&RDA;author” bb:valueURI=“&33987687” bb:valueDisplay=“Smith, John” … etc. …. /> One day, the bibliographic citation in a document may be able to make use of the same structure that underlies the library catalog. This will make linking more accurate between different uses of the same bibliographic entry.
  24. 25. Integration <ul><li>Library data will be available to all bibliographic applications on the Web </li></ul><ul><li>There will be an integrated bibliographic universe </li></ul><ul><li>There will be more of a connection between documents, bibliographies and the library catalog </li></ul><ul><li>There will be more re-use of the cataloging done by libraries </li></ul>
  25. 26. What will be the effect on libraries and librarians? <ul><li>RDF will be in the background behind cataloging and the catalog </li></ul><ul><li>There will be little obvious difference to users </li></ul><ul><li>There will be much more of a possibility to develop software and services based on library metadata </li></ul><ul><li>You won’t need to learn RDF to do your job! </li></ul>
  26. 27. This becomes the norm
  27. 28. Some useful links
  28. 29. Thank you Karen Coyle [email_address]