europeana and open data robina clayphan interoperability manager, europeana ldbc tuc meeting, 19...
TRANSCRIPT
Europeana and Open DataRobina Clayphan
Interoperability Manager, Europeana
LDBC TUC meeting, 19 November, 2013
What is Europeana?
• Europeana is a service that brings together digital content from across the cultural heritage domain in Europe
• It makes the metadata freely available
• It is a catalyst for change in the world of cultural heritage.
• Our vision: We believe in making cultural heritage openly accessible in a digital way, to promote the exchange of ideas and information.
Europeana.eu, Europe’s cultural heritage portal
Museums
National Aggregators
Regional Aggregators
Archives
Thematic collections
Libraries
- A network of participants in development and innovation- Nearly 30 million objects from 2,400 European galleries, museums, archives
and libraries
What types of objects does Europeana give access to?
Text Image Video Sound 3D
Europeana and open data
What Europeana makes available
Metadata
Link to digital objects online
Metadata (descriptive object information)
Different options:Open – not fully open (but clear) – Not open
Two categories of rights
CC
The Europeana Data Model
EDM requirements & principles
1. Distinction between “provided objects” (painting, book, movie, etc.) and their digital representations
2. Distinction between objects and metadata records describing an object
3. Allow for multiple records for a same object, containing potentially contradictory statements about it
4. Support for objects that are composed of other objects
5. Support for contextual resources, including concepts from controlled vocabularies
Richer metadata with finer granularity
Provide more semantics to the data
Build a semantic layer on top of Cultural Heritage objects
EDM Classes
ore:Aggregation(Identifier of aggregation)
edm:WebResource(Identifier of web resource)
edm:ProvidedCHO(Identifier of real object)
An aggregation with a provided CHO and a web resource
The three core classes
edm:aggregatedCHO
edm:hasView
The Aggregation with metadata
Properties for the Aggregation
Mandatory:
edm:aggregatedCHO
edm:dataProvider
edm:isShownBy or
edm:isShownAt
edm:provider
edm:rights
Optional:
edm:hasView
edm:object
dc:rights
edm:ugc
The aggregation represents the set of related resources about one real object contributed by one provider. It carries the metadata that is about the whole set
Properties for the ProvidedCHO
The ProvidedCHO is the cultural heritage object which is the subject of the package of data that has been submitted to Europeana.
Properties: dc:contributor, dc:coverage, dc:creator, dc:date, dc:description, dc:format, dc:identifier, dc:language, dc:publisher, dc:relation, dc:rights, dc:source,dc:subject, dc:title, dc:type, dcterms:alternative, dcterms:extent, dcterms:temporal, dcterms:medium, dcterms:created, dcterms:provenance, dcterms:issued, dcterms:conformsTo, dcterms:hasFormat, dcterms:isFormatOf, dcterms:hasVersion, dcterms:isVersionOf, dcterms:hasPart, dcterms:isPartOf, dcterms:isReferencedBy, dcterms:references, dcterms:isReplacedBy, dcterms:replaces dcterms:isRequiredBy, dcterms:requires dcterms:tableOfContents
edm:isNextInSequence
edm:isDerivativeOf
edm:currentLocation…
Properties for the web resource
One or more digital representations of the provided cultural heritage object.
dc:description dc:format dc:rights dc:sourcedcterms:conformsTo dcterms:createddcterms:extent dcterms:hasPart dcterms:isFormatOf dcterms:isPartOf dcterms:issuededm:isNextInSequence edm:rights
EDM Classes
Contextual classes
Representing (real-world) entities related to a provided object
as fully fledged resources, not just strings
edm:Agent
foaf:name
skos:altLabel
rdaGr2:biographicalInformation
rdaGr2:dateOfBirth….
skos:Concept
skos:prefLabel
skos:altLabel
skos:broader
skos:definition….
edm:TimeSpan skos:prefLabel
dcterms:isPartOf
edm:begin
edm:end….
edm:Placewgs84_pos:lat
wgs84_pos:long
skos:prefLabel
dcterms:isPartOf….
Example of a CHO with two contextual classes
dc:creator
dc:subject
Accessing and re-using Europeana data
How do users access Europeana content?
Europeana aims to provide content in the users’ workflow – where they want it, when they want it.
User focused channels: Europeana.eu portal, social media exports
For programmers: API, search widget, semantic mark up, LOD pilot
Europeana’s infrastructure is open for re-use
Europeana data available via
API
Search widgets
Semantic mark-up (schema.org) on portal
Linked Open Data pilot
http://pro.europeana.eu/api
http://data.europeana.eu
Some (approximate) numbers
Europeana database – 30 Million objects
LOD pilot – a subset of 20 Million objects
• contained nearly 1 Billion RDF explicit statements
• 4 Billion once you do all the RDF reasoning (sub-properties, sub-classes, etc) in OWLIM
• Ontotext has already loaded a chunk of data and is working on the update of it, in Europeana Creative.
Possible benchmarking queries?
Queries for exploring the dataset
• e.g. to generate the complete ordered list of Europeana aggregators and the data providers they gather
Queries for exploring the objects
• e.g. a list of works with a matching location/creator/title
• Simple graph traversal
Expressing EDM constraints (that cannot be done in OWL)
• Can RDF validation help e.g where at least one of two properties must be present (title or description)?
Queries to assist in data quality improvement
• Broken links, duplicates (or near duplicates), missing mandatory properties, missing thumbnails etc etc
For Information: We are starting a data quality task force if you are interested!
Useful links
Europeana portal europeana.eu
Europeana Professional pro.europeana.eu
• EDM documentation http://pro.europeana.eu/edm-documentation
• Europeana API http://www.europeana.eu/portal/api-introduction.html
• LOD pilot http://data.europeana.eu
Data Quality task force – [email protected]
Europeana Professional blog pro.europeana.eu/blog
Facebook facebook.com/Europeana
Twitter twitter.com/EuropeanaEU
Europeana Thought Lab pro.europeana.eu/thoughtlab/
Europeana end-user blog blog.europeana.eu/
Bonus slides!
EDM design requirements
Compatibility with different levels of description
• Allow different levels of granularity
• A book, a page, a detail of an image
Standard metadata format that can be specialized
• Allow the specification of domain specific application profiles
• Enable the re-use of existing standards
• Allow the extension of the initial model
EDM basis
OAI ORE (Open Archives Initiative Object Reuse & Exchange) for organizing an object’s metadata and digital representation(s)
Dublin Core for descriptive metadata
SKOS (Simple Knowledge Organization System) for conceptual vocabulary representation
CIDOC-CRM for the modeling of event and relationships between objects
Use the Semantic Web representation principles• RDF
• Re-use and mix different vocabularies together
• Preserve original data and still allow for interoperability
EDM Properties (excluding ESE)
Two providers and two aggregations(the same object)
31
aggregation of DMF
aggregation of Louvre
v
provenancemetadata
provenancemetadata
Cultural heritage object
Europeanaaggregation
Enriched metadata
Landing page