1. kcoyle@kcoyle.net Yes, we can! Some observations on library linked data

2. kcoyle@kcoyle.net What is the answer?

3. kcoyle@kcoyle.net What is the question?

4. kcoyle@kcoyle.net What do we do?

5. kcoyle@kcoyle.net Why do we do it?

6. kcoyle@kcoyle.net Cataloging Distinguish Differentiate Separate

7. kcoyle@kcoyle.net Cataloging Distinguish Differentiate Separate

8. kcoyle@kcoyle.net Is this the same book? Or Is this a different book?

9. kcoyle@kcoyle.net "Books are a slow conversation" Each one listens to others and talks to others.

10. kcoyle@kcoyle.net

11. Today's tools and models  MARC (at the end of its life)‏

13. kcoyle@kcoyle.net Today's tools and models  MARC (at the end of its life)‏  FRBR (a model, but based on past practices; unstable)‏  RDA (based on FRBR and AACR and MARC, with some new concepts)‏.

14. Where are we going?

15. Further

16. kcoyle@kcoyle.net Cutter's questions What books does the library have by this author? What books does the library have on this topic? Does the library have a book with this title?

17. kcoyle@kcoyle.net Tomorrow's questions Starting with this author, what authors are related to him/her through their subject matter? Which are closest to this author? Who else was writing in this time in this place? Given this subject, who are the key authors?

18. kcoyle@kcoyle.net Day after tomorrow's questions Where does this subject lead me? What resources (library or outside of library)? What are related subjects? Information about the subject (encyclo/wiki/pedia)‏

19. kcoyle@kcoyle.net What is further? Semantic web – ending the library data silo Navigation and discovery instead of search Computable data – ability to mine bibliographic data for information..

20. kcoyle@kcoyle.net Linking is not destructive

21. kcoyle@kcoyle.net Reorganize around new entities Persons Subjects

22. kcoyle@kcoyle.net Entities can interact Persons Subjects

23. kcoyle@kcoyle.net Open Library http://openlibrary.org

29. Everything is connected to something No (or few) dead ends Computation is "easy" (e.g. topic maps, term clouds, timelines) ‏ Users can discover previously unseen connections between information resources.

30. kcoyle@kcoyle.net Back to our tools FR's – FRBR, FRAD, FRSAD RDA

31. kcoyle@kcoyle.net Perfect, or perfected? Not yet

32. kcoyle@kcoyle.net FRBR Work Item Expression Manifestation E-R Model?

33. kcoyle@kcoyle.net FRBR Work Item Expression Manifestation Corp Person

34. kcoyle@kcoyle.net FRBR Work Item Expression Manifestation Event Object Place Concept Corp Person

35. kcoyle@kcoyle.net FRBR Work Item Expression Manifestation Event Object Place Concept Corp Person

36. kcoyle@kcoyle.net FRBR – bibliographic relationships Work Item Expression Manifestation Work Expression

37. kcoyle@kcoyle.net http://kcoyle.net/rda

38. kcoyle@kcoyle.net Some issues - FRBR Not well understood Untested, mostly unimplemented Superceded by FRAD, FRSAD, and now requiring changes to be compatible May not interact well with non-FRBR data.

39. kcoyle@kcoyle.net More issues - FRBR Group 3 (Subjects) should be replaced with a general subject relationship to anything that can be identified Group 3 elements should be general (e.g. Place) or be subproperties of a more general property Placement of data elements within WEMI is highly debated, especially for collective items (books of essays, multiple music works on a disk)‏.

40. FR for Authority Data (FRAD)‏ Person Corp Family

41. FR for Authority Data Person Corp Family Identification name Controlled access point Rules Agency

42. FR for Authority Data Person Corp Family Identification name Controlled access point Rules Agency Is basis for using Assigned by

43. FR for Subject Authority Data (FRSAD)‏ Work Is subject Event Object Place Concept FRBR

44. FR for Subject Authority Data (FRSAD)‏ Work Thema Nomen Has subject Has name

45. RDA RDA is at least 3 things: Cataloging guidance Ontology (not entirely "linked data" compatible)‏ Definition of values (most are text; some controlled lists, but most mix list and text)‏

46. kcoyle@kcoyle.net Some issues - RDA Not well understood Untested, mostly unimplemented Adheres strictly to FRBR - Every RDA element is valid only as a single FRBR entity.

47. RDA Properties Extent (Manifestation)‏ Extent (Item)‏ Extent of still image (Manifestation)‏ Extent of still image (Item)‏

48. kcoyle@kcoyle.net Some issues - RDA There is no data carrier defined for RDA.

49. RDA in RDF Joint project between DCMI and RDA April, 2007

51. http://metadataregistry.org RDA – properties, relationships, controlled values; still provisional FRBRer - completed FRAD – in progress ISBD – in review

55. RDA Generalized Properties Extent Extent (Manifestation)‏ Extent (Item)‏ Extent of still image Extent of still image (Manifestation)‏ Extent of still image (Item)‏

58. US RDA "Test" Great opposition to RDA in US "Test" as proof of concept "Test" uses MARC; ignores all FRBR and RDF- type aspects Only tests that RDA guidance can be used to complete MARC records

59. US RDA "Test" September, 2010 – December 2010 ~30 libraries Final report March, 2011 Next: RDA will be accepted

60. To Do Test FRBR and RDA in a linked data environment Simplify where possible Create links between library data and non- library metadata Encourage use of library data outside of libraries Encourage use of non-library data inside libraries.

61. Get LLD expertise into library standards process

62. Thank you! http://kcoyle.net kcoyle@kcoyle.net