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.
Linking library and theatre data Lukas Koster Library Systems Coordinator Library of the University of Amsterdam http://ww...
Pilot project Linking library catalogue data to theatre performance data Dutch Digital Cultural Heritage Foundation DEN as...
Pilot Objectives <ul><li>Proof of concept </li></ul><ul><li>Gather experience </li></ul><ul><li>Added value for customers ...
Why, what, how, what not, results, problems, solutions?
Libraries are meant to be gateways to information
Helping customers find information
<ul><li>Information used to be stored in physical items </li></ul><ul><li>books </li></ul><ul><li>journals </li></ul><ul><...
Services for customers Support finding information Give access to information WWW
Information is everywhere, elsewhere
People  Objects  Newspapers Museums Publishers Books  Files  Archives  Libraries   Digital  Physical Images Text Memories ...
Different contexts Subject area Theatre Godot Personal context Library context Ad Aerts  (@adaerts) Search No connection
Catalogue results
Catalogue results
Catalogue results Library  catalogue = logistics and inventory system for storing and transporting physical items
Catalogue results Bibliographic metadata: description of physical attributes, location, availability
Nothing about the content
Library delivery
Theatre play <ul><li>Samuel Beckett </li></ul><ul><li>En attendant Godot (1949) </li></ul><ul><li>Waiting for Godot – a tr...
Theatre context <ul><li>PARADOX </li></ul><ul><li>Key concept: The Performance </li></ul><ul><li>Nothing remains, except ‘...
Theatre context http://theaterinstituut.adlibsoft.com/
Theatre context
Theatre context
Can we connect both contexts using linked data?
Two sides Publish Use
Publishing linked data URIs for all things Preferably persistent   Return data in ‘machine readable format’ Triples/RDF/et...
Using linked data 1. Construct URIs based on native metadata 2. Process returned RDF/Triples/etc. 3. Present results
A theatre play data model ‘ Play ’
Theatre Things (Entities) <ul><li>Authors, actors, producers, etc. (persons) </li></ul><ul><li>Plays (shows) </li></ul><ul...
Library Things (Entities) <ul><li>Authors (persons) </li></ul><ul><li>Books/holdings/items (plays) </li></ul>
Matching <ul><li>Library catalogue results – Theatre production database results </li></ul>
What we made
How we did it <ul><li>URIs from TIN database </li></ul><ul><ul><li>< base-url >/ person /< personname > </li></ul></ul><ul...
How we did it - URIs < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot JavaScript/J...
How we did it – JavaScript/JQuery < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot...
Problems <ul><li>No common identifiers </li></ul><ul><ul><li>Aleph key  ≠  key </li></ul></ul><ul><li>No internal links to...
Identifiers/URIs/String matching /title/Beckett, Samuel/Waiting for Godot /title/Beckett, Samuel/Waiting for Godot : a tra...
Solutions? <ul><li>Add links:  </li></ul><ul><ul><li>Internally: FRBR </li></ul></ul><ul><ul><li>Externally: Authority fil...
Links: FRBR, and more Waiting  for Godot Wachten op Godot (NL) En attendant Godot (FR) Production 2009 Production 2010 Per...
Ideally….
Current situation Implicit relations
Legacy systems => Linked Data <ul><li>Make implicit relations explicit </li></ul><ul><li>Use external authority files </li...
‘ 1st edition 1956, 1st print of this edition 1965’ ‘ Original title: En attendant Godot’ Links as text strings
MARC MARC record: - Identifiers to union catalogue records - Subfields with Autor name; Main title
JavaScript/JQuery HTML < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot < base-url...
$8 – Field link and sequence number Identifies linked fields and may also propose a sequence for the linked fields. Subfie...
 
 
Worldcat Identities Dutch Union Catalogue PICA - OCLC Digital Author Identifier
 
 
Dutch Union Catalogue PICA - OCLC
 
 
 
 
Cataloguing: linking FRBR Author Work RDA Author Work
Upcoming SlideShare
Loading in …5
×

Linking library and theatre data

2,137 views

Published on

Cataloguing and Indexing Group Scotland - 'Linked Data and the Semantic Web - what have libraries got to do with it?'
National Library of Scotland, June 17, 2011
http://www.slainte.org.uk/events/EvntShow.cfm?uEventID=2671

  • Be the first to comment

Linking library and theatre data

  1. 1. Linking library and theatre data Lukas Koster Library Systems Coordinator Library of the University of Amsterdam http://www.uba.uva.nl @lukask Linked Data and the Semantic Web – CIGS June 17 2011, Edinburgh
  2. 2. Pilot project Linking library catalogue data to theatre performance data Dutch Digital Cultural Heritage Foundation DEN as instigator http://den.nl/ Library of the University of Amsterdam Theatre Institute of The Netherlands http://tin.nl/ http://www.uba.uva.nl/
  3. 3. Pilot Objectives <ul><li>Proof of concept </li></ul><ul><li>Gather experience </li></ul><ul><li>Added value for customers </li></ul><ul><li>Set an example </li></ul><ul><li>Convince cultural heritage institutions </li></ul><ul><li>Convince TIN, UBA management </li></ul>
  4. 4. Why, what, how, what not, results, problems, solutions?
  5. 5. Libraries are meant to be gateways to information
  6. 6. Helping customers find information
  7. 7. <ul><li>Information used to be stored in physical items </li></ul><ul><li>books </li></ul><ul><li>journals </li></ul><ul><li>cds </li></ul><ul><li>dvds </li></ul>
  8. 8. Services for customers Support finding information Give access to information WWW
  9. 9. Information is everywhere, elsewhere
  10. 10. People Objects Newspapers Museums Publishers Books Files Archives Libraries Digital Physical Images Text Memories Movies Music Sound Statistics Research Journals Data Maps Metadata Collections Buildings History Art Science Government Societies Stories Photos Reports Private Public Games Shows Education Nature Speech War Schools Love Theatre Poetry Location Fiction Facts Fantasy Animals
  11. 11. Different contexts Subject area Theatre Godot Personal context Library context Ad Aerts (@adaerts) Search No connection
  12. 12. Catalogue results
  13. 13. Catalogue results
  14. 14. Catalogue results Library  catalogue = logistics and inventory system for storing and transporting physical items
  15. 15. Catalogue results Bibliographic metadata: description of physical attributes, location, availability
  16. 16. Nothing about the content
  17. 17. Library delivery
  18. 18. Theatre play <ul><li>Samuel Beckett </li></ul><ul><li>En attendant Godot (1949) </li></ul><ul><li>Waiting for Godot – a tragicomedy in two acts (1952) </li></ul><ul><li>A country road </li></ul><ul><li>A tree </li></ul><ul><li>Evening </li></ul><ul><li>Men in bowler hats </li></ul>
  19. 19. Theatre context <ul><li>PARADOX </li></ul><ul><li>Key concept: The Performance </li></ul><ul><li>Nothing remains, except ‘residuals’/’waste products’: </li></ul><ul><li>Memories </li></ul><ul><li>Souvenir brochures </li></ul><ul><li>Recordings </li></ul><ul><li>Objects </li></ul><ul><li>Texts </li></ul><ul><li>Reviews </li></ul><ul><li>Metadata </li></ul>
  20. 20. Theatre context http://theaterinstituut.adlibsoft.com/
  21. 21. Theatre context
  22. 22. Theatre context
  23. 23. Can we connect both contexts using linked data?
  24. 24. Two sides Publish Use
  25. 25. Publishing linked data URIs for all things Preferably persistent Return data in ‘machine readable format’ Triples/RDF/etc. Vocabulary/ontology
  26. 26. Using linked data 1. Construct URIs based on native metadata 2. Process returned RDF/Triples/etc. 3. Present results
  27. 27. A theatre play data model ‘ Play ’
  28. 28. Theatre Things (Entities) <ul><li>Authors, actors, producers, etc. (persons) </li></ul><ul><li>Plays (shows) </li></ul><ul><ul><li>Productions </li></ul></ul><ul><ul><li>Performances </li></ul></ul><ul><li>Digital objects </li></ul><ul><ul><li>Photos, posters, sound, video </li></ul></ul><ul><li>Physical objects </li></ul><ul><ul><li>Costumes, scenery, models, posters, photos, sound, video … </li></ul></ul>
  29. 29. Library Things (Entities) <ul><li>Authors (persons) </li></ul><ul><li>Books/holdings/items (plays) </li></ul>
  30. 30. Matching <ul><li>Library catalogue results – Theatre production database results </li></ul>
  31. 31. What we made
  32. 32. How we did it <ul><li>URIs from TIN database </li></ul><ul><ul><li>< base-url >/ person /< personname > </li></ul></ul><ul><ul><li>< base-url >/ title /< personname >/< title > </li></ul></ul><ul><ul><li>< base-url >/ production /< personname >/< title >/< opening date > </li></ul></ul>Requested by OPAC Returned by TIN Together with data
  33. 33. How we did it - URIs < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot JavaScript/JQuery HTML
  34. 34. How we did it – JavaScript/JQuery < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot <base-url>/ production/Beckett, Samuel/Waiting for Godot/1988-11-22/6750 JavaScript/JQuery
  35. 35. Problems <ul><li>No common identifiers </li></ul><ul><ul><li>Aleph key ≠ key </li></ul></ul><ul><li>No internal links to common entity </li></ul><ul><ul><li>No central “ Work ” </li></ul></ul><ul><li>String matching </li></ul><ul><ul><li>Author: ‘ Samuel Beckett ’- ‘ Beckett, Samuel ’ </li></ul></ul><ul><ul><li>Title: ‘ Waiting for Godot ’ – ’En attendant Godot ’ </li></ul></ul><ul><li>Copyright </li></ul><ul><ul><li>Photos, videos, audio, artwork </li></ul></ul>
  36. 36. Identifiers/URIs/String matching /title/Beckett, Samuel/Waiting for Godot /title/Beckett, Samuel/Waiting for Godot : a tragicomedy in two acts /title/Beckett, Samuel/En attendant Godot : pièce en deux actes /title/Beckett, Samuel/Wachten op Godot /title/Beckett, Samuel/Waiting for Godot /title/Beckett, Samuel/Waiting For Godot /title/Beckett, Samuel/Wachten op Godot /title/Beckett, Samuel/Wachtend op Godot /title/Beckett, Samuel/Wachten op Godot (De favorieten) /title/Beckett, Samuel/Wachten op Godot (eerste bedrijf) /title/Beckett, Samuel/En attendant Godot /title/Beckett, Samuel/Warten auf Godot
  37. 37. Solutions? <ul><li>Add links: </li></ul><ul><ul><li>Internally: FRBR </li></ul></ul><ul><ul><li>Externally: Authority files </li></ul></ul><ul><li>Smart string matching? </li></ul><ul><li>Manually? </li></ul><ul><li>External broker mechanism </li></ul>
  38. 38. Links: FRBR, and more Waiting for Godot Wachten op Godot (NL) En attendant Godot (FR) Production 2009 Production 2010 Performance 1 Performance 2 Performance 3 Manifestation Item Work Expression 1st Edition 2007 2nd Edition 2010 Copy 1 Copy 2 Copy 3 Theatre Text/Publisher/Library FRBR Video registration Article Scene 1 Scene 2 Scene 3 Photo Library Catalogue
  39. 39. Ideally….
  40. 40. Current situation Implicit relations
  41. 41. Legacy systems => Linked Data <ul><li>Make implicit relations explicit </li></ul><ul><li>Use external authority files </li></ul>
  42. 42. ‘ 1st edition 1956, 1st print of this edition 1965’ ‘ Original title: En attendant Godot’ Links as text strings
  43. 43. MARC MARC record: - Identifiers to union catalogue records - Subfields with Autor name; Main title
  44. 44. JavaScript/JQuery HTML < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot < base-url >/person/068463928 < base-url >/title/841548528
  45. 45. $8 – Field link and sequence number Identifies linked fields and may also propose a sequence for the linked fields. Subfield $8 may be repeated to link a field to one or more other group of fields http://www.loc.gov/marc/bibliographic/ecbdcntf.html
  46. 48. Worldcat Identities Dutch Union Catalogue PICA - OCLC Digital Author Identifier
  47. 51. Dutch Union Catalogue PICA - OCLC
  48. 56. Cataloguing: linking FRBR Author Work RDA Author Work

×