Linking library and theatre data

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

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/

Pilot Objectives
Proof of concept
Gather experience
Added value for customers
Set an example
Convince cultural heritage institutions
Convince TIN, UBA management

Why, what, how, what not, results, problems, solutions?

Libraries are meant to be gateways to information

Helping customers find information

Information used to be stored in physical items
books
journals
cds
dvds

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 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

Different contexts Subject area Theatre Godot Personal context Library context Ad Aerts (@adaerts) Search No connection

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
Samuel Beckett
En attendant Godot (1949)
Waiting for Godot – a tragicomedy in two acts (1952)
A country road
A tree
Evening
Men in bowler hats

Theatre context
PARADOX
Key concept: The Performance
Nothing remains, except ‘residuals’/’waste products’:
Memories
Souvenir brochures
Recordings
Objects
Texts
Reviews
Metadata

Theatre context http://theaterinstituut.adlibsoft.com/

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/etc. Vocabulary/ontology

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)
Authors, actors, producers, etc. (persons)
Plays (shows)
Productions
Performances
Digital objects
Photos, posters, sound, video
Physical objects
Costumes, scenery, models, posters, photos, sound, video …

Library Things (Entities)
Authors (persons)
Books/holdings/items (plays)

Matching
Library catalogue results – Theatre production database results

What we made

How we did it
URIs from TIN database
< base-url >/ person /< personname >
< base-url >/ title /< personname >/< title >
< base-url >/ production /< personname >/< title >/< opening date >
Requested by OPAC Returned by TIN Together with data

How we did it - URIs < base-url >/person/Beckett, Samuel < base-url >/title/Beckett, Samuel/Waiting for Godot JavaScript/JQuery HTML

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

Problems
No common identifiers
Aleph key ≠ key
No internal links to common entity
No central “ Work ”
String matching
Author: ‘ Samuel Beckett ’- ‘ Beckett, Samuel ’
Title: ‘ Waiting for Godot ’ – ’En attendant Godot ’
Copyright
Photos, videos, audio, artwork

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

Solutions?
Add links:
Internally: FRBR
Externally: Authority files
Smart string matching?
Manually?
External broker mechanism

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

Ideally….

Current situation Implicit relations

Legacy systems => Linked Data
Make implicit relations explicit
Use external authority files

‘ 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 >/person/068463928 < base-url >/title/841548528

$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

Worldcat Identities Dutch Union Catalogue PICA - OCLC Digital Author Identifier

Dutch Union Catalogue PICA - OCLC

Cataloguing: linking FRBR Author Work RDA Author Work

Linking library and theatre data

by Lukas Koster on Jun 18, 2011

Accessibility

Tags

Upload Details

Usage Rights

Statistics

Linking library and theatre data — Presentation Transcript