Talk given at the DISH 2011 workshop on "new models for interaction for GLAMs (slides by Judith van Gent and Victor de Boer)

1. Amsterdam Museum
as
Five-star Linked Data
Judith van Gent Victor de Boer

3. Collection Amsterdam Museum
– More than 75.000 objects
paintings, drawings, prints, coins, statues, photos, glass,
silver, furniture, ceramics, books, historic interiors,
costumes, textiles, clocks, shoes, etc.
– Around 20% on show, rest in storage depots

4. Collection Amsterdam Museum
– of the Amsterdam people
– of international importance
– sharing data/knowledge is policy

5. 2010 AM entire collection online
• digital depot
• CC BY-SA
• not all data optimal
• public can react/contribute

6. AM open data
– Use and reuse!
– Adlib database open
– Adlib API (XML output)
– OAI-PMH (XML, Dublin Core)
– Linked Open Data (VU EDM)
– Metadata / images
– Spectrum, Dublin Core, Texts
–Persistent id i.o.
–id.amsterdammuseum.nl/collection/123

7. • OAI protocol
– Digitalecollectie.nl > Europeana
– ED*IT
– Oneindig NH
• Wikipedia
• Adlib API
– iPhone app
– Apps for Amsterdam

14. Linked Data
“Linking Open Data cloud diagram, by Richard Cyganiak and Anja Jentzsch. http://lod-cloud.net/”

17. Why linked data (1/2)
Slide stolen from Christophe Gueret

18. Why linked data (2/2)
Slide stolen from Christophe Gueret

19. Europeana
• “Europeana enables people to explore the digital
resources of Europe's museums, libraries, archives and
audio-visual collections.’’
www.europeana.eu
From portal… …to data aggregator.

20. AM metadata
<record priref="10541“ >
• Adlib database XML API <acquisition.date>1997</acquisition.date>
<dimension>
<dimension.type>hoogte</dimension.type>
<dimension.unit>cm</dimension.unit>
<dimension.value>6</dimension.value>
• Object metadata …
</dimension>
• 73.000 objects, 256MB </record>
• Nested XML
• Concept Thesaurus <record priref="28024“ >
<term>Kalverstraat 124</term>
<broader_term>Kalverstraat</broader_term>
• 27.000, 9MB <term.type>GEOKEYW </term.type>
• Different types (geo,motif, event) </record>
• Person ‘Thesaurus’ <record priref="6" >
• 67.000 persons, 10MB <biography>boekverkoper en uitgever van
cartografie</biography>
• Consolidated from object metadata fields <birth.date.start>1659</birth.date.start>
• Creators, annotators, reproduction <death.date.start>1733</death.date.start>
<name>Aa, Pieter van der</name>
creators, institutions, <nationality>Nederlands</nationality>
<use>Aa, Pieter van der (I)</use>
</record>

21. Four rules of 5-star Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those
names.
3. When someone looks up a URI, provide useful
information, using the standards (RDF*, SPARQL)
4. Include links to other URIs. so that they can
discover more things.
http://www.w3.org/DesignIssues/LinkedData.html

22. Amsterdam Museum URIs
• PURL basename: http://purl.org/collections/nl/am/
• Objects: Use “prirefs”, prefixed by “proxy-”
– http://purl.org/collections/nl/am/proxy-63432
• Concepts & Persons: Use “prirefs”, prefixed by “p-”, or “t-”
– http://purl.org/collections/nl/am/p-201
• Properties (schema): Use XML element name
– http://purl.org/collections/nl/am/acquisition.date

23. Four rules of 5-star Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up those
names.
3. When someone looks up a URI, provide useful
information, using the standards (RDF*, SPARQL)
4. Include links to other URIs. so that they can
discover more things.
http://www.w3.org/DesignIssues/LinkedData.html

24. XMLRDF
• Modular setup
1. Start with XML (OAI-harvest)
2. Syntactic transformation to RDF
3. Rewrite raw RDF using simple rules
4. Define mapping schema to EDM/other

25. RDF conversion (XMLRDF)
<record priref="19319 “ >
<date>1651</date>
<maker>Rembrandt (1606-1669)</maker>
<object.type>etsplaat</object.type> priref “19319 ”
… date
</record>
“1651”
am:Record
_:bn1 “Rembrandt (1606-1669)”
object.type “etsplaat”
“19319 ”
am:date “1651”
“1234”
am:priref
am:Record am:birthdate
am:maker am:Person
am:proxy-19319 “1606”
am:p-1234
rda:name “Rembrandt”
skos:Concept
am:etsplaat
“etsplaat”
skos:prefLabel

26. Mapping schema
dcterms:created
rdfs:subPropertyOf
am:productiondateStart
1770
am:proxy_22093
am:productiondateEnd
1790

27. Cliopatria
SPARQL-app Browser
Purl.org
redirect
SPARQL Web interface
HTTP server
RDF(s) storage Logic
Prolog
http://semanticweb.cs.vu.nl/

28. text/html

29. application/rdf+xml
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rdf:RDF [
<!ENTITY am 'http://purl.org/collections/nl/am/'>
<!ENTITY rdf 'http://www.w3.org/1999/02/22-rdf-syntax-ns#'>
<!ENTITY skos 'http://www.w3.org/2004/02/skos/core#'> ]>
<rdf:RDF xmlns:am="&am;" xmlns:rdf="&rdf;" xmlns:skos="&skos;" >
<skos:ConceptScheme rdf:about="&am;AM_ConceptScheme"/>
<skos:Concept rdf:about="&am;t-1" am:priref="1"> <am:termType rdf:resource="&am;t-
termtypeGEOKEYW"/> <am:termType rdf:resource="&am;t-termtypePLACE"/> <skos:broader
rdf:resource="&am;t-2688"/> <skos:inScheme rdf:resource="&am;AM_ConceptScheme"/> <skos:prefLabel
xml:lang="nl">Wassenaar</skos:prefLabel> </skos:Concept>
<skos:Concept rdf:about="&am;t-10" am:priref="10"> <am:termType rdf:resource="&am;t-
termtypeGEOKEYW"/> <am:termType rdf:resource="&am;t-termtypePLACE"/> <skos:broader
rdf:resource="&am;t-12"/> <skos:inScheme rdf:resource="&am;AM_ConceptScheme"/> <skos:prefLabel
xml:lang="nl">Driebergen</skos:prefLabel> </skos:Concept>
<skos:Concept rdf:about="&am;t-100" am:priref="100"> <am:termType rdf:resource="&am;t-
termtypeGEOKEYW"/> <am:termType rdf:resource="&am;t-termtypePLACE"/> <skos:broader
rdf:resource="&am;t-12"/> <skos:inScheme rdf:resource="&am;AM_ConceptScheme"/> <skos:narrower
rdf:resource="&am;t-31297"/> <skos:prefLabel xml:lang="nl">Naarden</skos:prefLabel> </skos:Concept>
<skos:Concept rdf:about="&am;t-1000" am:priref="1000"> <am:termType rdf:resource="&am;t-
termtypePLACE"/> <skos:inScheme rdf:resource="&am;AM_ConceptScheme"/> <skos:prefLabel
xml:lang="nl">Clos-Lucé</skos:prefLabel> </skos:Concept>

30. SPARQL
http://semanticweb.cs.vu.nl/europeana/user/query

31. Again, the rules of Linked Data
1. Use URIs as names for things
2. Use HTTP URIs so that people can look up
those names.
3. When someone looks up a URI, provide
useful information, using the standards
(RDF*, SPARQL)
4. Include links to other URIs. so that they can
discover more things.
http://www.w3.org/DesignIssues/LinkedData.html

32. Link to other sources
“19319 ”
am:date “1651”
“1234”
am:priref
am:Record am:birthdate
am:maker am:Person
am:proxy-19319 “1606”
am:p-1234
rda:name “Rembrandt”
owl:sameAs (?)
Viaf:nationality
Viaf:Person “Dutch”
Viaf:RebrandtvanRijn
“Rembrandt
Harmensz.
rdfs:label
Van Rijn”

33. Amalgame alignment platform
• Semi-automatic linking
– Simple automatic
techniques,
– chained together by hand
• 3500+ links put in RDF
– 143 places linked to
GeoNames
– 1076 persons linked to
ULAN (VIAF)
– 34 persons linked to
DBPedia
– 2498 concepts AATNed.

34. CKAN Data Hub
http://thedatahub.org/dataset/amsterdam-museum-as-edm-lod

35. And now applications!…right??

36. Plaatsen van Betekenis
Local Linked Data (Amsterdam)

38. end
v.de.boer@vu.nl
j.vangent@amsterdammuseum.nl
amsterdammuseum.nl
http://collectie.ahm.nl/
http://amdata.adlibsoft.com/wwwopac.ashx
http://semanticweb.cs.vu.nl/lod/am/

39. EDM

40. What kind of RDF?
• Europeana Data Model (EDM)
– Keep original metadata intact
– Use sem web (LD) principles: RDF
• Re-use of standard models
– Dublin Core for metadata representation
• creator, date, title etc.
– SKOS for vocabularies
• preferredLabel, hasBroader, etc.
– OAI-ORE to allow for aggregations etc.

41. EDM voorbeeld
Provenance
+web
views/plaatjes
proxy
object
metadata
Aggregation
Physical Object
geen
metadata