Europeana Network Association Members Council Meeting, Milan - Europeana & EYCH
Europeana, more than data aggregation?
-
Upload
antoine-isaac -
Category
Technology
-
view
738 -
download
1
Transcript of Europeana, more than data aggregation?
Europeana, more than data aggregation?
Antoine Isaac
Europeana
UvA Digital Heritage mini-symposium, Dec. 12, 2013
Europeana.eu, Europe’s cultural heritage portal
Text
Image
Video
Sound
3D
30M objects from 2,200 galleries, museums, archives and libraries
Who submits data to Europeana?
Domain Aggregators National initiatives
Audiovisual collections
National Aggregators
Regional Aggregators
Archives
Thematic collections
Libraries
e.g. Musées Lausannois
e.g. Culture Grid,
Culture.fr
e.g. The European Library
e.g. APEX
e.g. EUScreen, European Film Gateway
e.g. Judaica Europeana, Europeana Fashion
Distributing Europeana content
Europeana aims to provide content in the users’ workflow – where they want it, when they want it.
Web portal, project portals/exhibitions, social media, app
Others using Europeana data independently
Unique point of access, with higher visibility
Europeana as infrastructure open for re-use
Available via
API
Search widgets
Semantic mark-up (schema.org) on portal
Linked Open Data
Providing publication services that smaller institutions may not be able to develop
Content (digital objects on the site of the provider)
Metadata (descriptive object information)
Different options
Facilitating re-use on the legal side
CC
Distinguishing two levels of rights
Rights Statements for content
Open
Not open – but clear
Not open – and not so clear
The framework is in continuous improvement!
Prior to EDM: ESE records
europeana:dataProvider
europeana:provider
europeana:isShownAt
europeana:isShownBy
europeana:object
europeana:rights
dc:contributor, dc:creator, dc:date, dc:format, dc:identifier, dc:language, dc:publisher, dc:relation, dc:source, 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
europeana:type
Flat model, no links e.g. between objects and context entities (persons, places)
Data on real object and digital content mixed in one record
A lot of mapping quality problems
Connecting to multilingual data
<skos:Concept rdf:about="http://www.mimo-db.eu/InstrumentsKeywords/2251"> <skos:prefLabel xml:lang="">Harpsichord</skos:prefLabel> <skos:prefLabel xml:lang="de">Cembalo</skos:prefLabel> <skos:prefLabel xml:lang="sv">Cembalo</skos:prefLabel> <skos:prefLabel xml:lang="fr">Clavecin</skos:prefLabel> <skos:prefLabel xml:lang="it">Clavicembalo</skos:prefLabel> <skos:prefLabel xml:lang="en">Harpsichord</skos:prefLabel> <skos:prefLabel xml:lang="nl">Klavecimbel</skos:prefLabel> <skos:broader> <skos:Concept rdf:about="http://www.mimo-db.eu/InstrumentsKeywords/2239"> <skos:prefLabel>Harpsichords</skos:prefLabel> </skos:Concept> </skos:broader></skos:Concept>
Various Types of Contextual Resources
<gn:Feature rdf:about="http://sws.geonames.org/3176959/"> <gn:name>Florence</gn:name> <gn:alternateName xml:lang="ko"> 피렌체 </gn:alternateName> <gn:alternateName xml:lang="ja"> フィレンツェ </gn:alternateName> <gn:alternateName xml:lang="th">ฟลอเรนซ์�</gn:alternateName> <gn:alternateName xml:lang="bo">ཧྥུ་ལོ� ་རོ� ན་ཟི� འུ་ཡ།</gn:alternateName> <gn:alternateName xml:lang="cy">Fflorens</gn:alternateName> <gn:alternateName xml:lang="bs">Firenca</gn:alternateName> <gn:alternateName xml:lang="hbs">Firenca</gn:alternateName> <gn:alternateName xml:lang="hr">Firenca</gn:alternateName> <gn:alternateName xml:lang="sq">Firenca</gn:alternateName> <gn:alternateName xml:lang="pl">Firence</gn:alternateName> <gn:alternateName xml:lang="sl">Firence</gn:alternateName> <gn:alternateName xml:lang="lij">Firense</gn:alternateName> <gn:population>371517</gn:population> <wgs84_pos:lat>43.76667</wgs84_pos:lat> <wgs84_pos:long>11.25</wgs84_pos:long>
Contextual Resources – Places
<gn:Feature rdf:about="http://sws.geonames.org/3176959/"> <gn:name>Florence</gn:name> <gn:alternateName xml:lang="ko"> 피렌체 </gn:alternateName> <gn:alternateName xml:lang="ja"> フィレンツェ </gn:alternateName> <gn:alternateName xml:lang="th">ฟลอเรนซ์�</gn:alternateName> <gn:alternateName xml:lang="bo">ཧྥུ་ལོ� ་རོ� ན་ཟི� འུ་ཡ།</gn:alternateName> <gn:alternateName xml:lang="cy">Fflorens</gn:alternateName> <gn:alternateName xml:lang="bs">Firenca</gn:alternateName> <gn:alternateName xml:lang="hbs">Firenca</gn:alternateName> <gn:alternateName xml:lang="hr">Firenca</gn:alternateName> <gn:alternateName xml:lang="sq">Firenca</gn:alternateName> <gn:alternateName xml:lang="pl">Firence</gn:alternateName> <gn:alternateName xml:lang="sl">Firence</gn:alternateName> <gn:alternateName xml:lang="lij">Firense</gn:alternateName> <gn:population>371517</gn:population> <wgs84_pos:lat>43.76667</wgs84_pos:lat> <wgs84_pos:long>11.25</wgs84_pos:long>
EDM is ready for metadata enrichment
Re-using third-party sources
• GEMET, GeoNames, DBpedia
Multilingual + semantic features
By providers or Europeana
• Hopefully in collaboration!
Benefiting from existing R&D
Re-using existing stuff: OAI-ORE, Dublin Core, SKOS…
EuropeanaTechcommunity
EDM is cross-community development involving library, archive and museum experts, plus academic partners
Not a strict standard, rather a common ground…
Europeana’s vision and mission
We believe in making cultural heritage openly accessible in a digital way, to promote the exchange of ideas and information.
We want to be a catalyst for change in the world of cultural heritage.
Aggregation is more than just gathering data!
Useful links
Europeana portal europeana.eu
Europeana Professional pro.europeana.eu
EuropeanaTech community pro.europeana.eu/europeana-tech
Europeana Data Model documentation pro.europeana.eu/edm-documentation
Europeana Twitter @EuropeanaEU
EuropeanaTech Twitter @EuropeanaTech