EDM for Europeana SoundsCécile Devarenne Operations Officer

Metadata training, Europeana Sounds project Athens, 23rd/24th of October 2014

Content

• What is the Europeana Data Model (EDM)? • What is the EDM profile for sounds? • Classes in EDM: edm:ProvidedCHO, ore:Aggregation,

edm:WebResource, contextual classes • edm:Collection, a subclass specified by the EDM profile for sounds • Connections in EDM • Representation of sounds cultural heritage objects in EDM • What is data quality in EDM: mandatory elements, rich

contextualized data and rich digital representations modeled in the best possible way from the source data

Most of the examples shown in the coming slides are descriptions of sounds or audio-related content

EDM: the Europeana Data Model

What is the Europeana Data Model?

• The EDM is a theoretical data model that allows data to be presented in different ways according to the practices of the various domains who contribute data to Europeana

• Before EDM, ESE: flat data model, data on real object and digital object mixed together, no links between objects and context (e.g agents and concepts and places)

• EDM was implemented to enable enhanced descriptive metadata

What is the EDM profile for sounds?

• The EDM profile for sounds is a set of recommendations for the adaptation of the current Europeana Data Model (EDM) for audio and audio-related objects

• It is the result of a consultation among participants of the Sounds project and its outcome is described in the report of the Task Force EDM profile for sounds

• It includes additional specific properties enabling a better description of sounds and audio-related objects

• It also includes two additional sub classes to EDM: edm:Collection and mo:MusicalGroup

What is the Europeana Data Model?

• All documentation on EDM is available on the Europeana Professional website: http://pro.europeana.eu/edm-documentation

• The main document to refer to to get a full understanding on the present implementation of the EDM schema is the EDM guidelines is downloadable here

• Main reference for guidance in mapping: all the properties described in the EDM guidelines are also listed as an Annex to the

EDM profile for sounds https://basecamp.com/1936492/projects/4984360/uploads/16914642?enlarge=111488668#attachment_111488668

EDM classes enabling the description of cultural heritage objects

• Three core classes: • edm:ProvidedCHO - the provided cultural heritage object

A music score • edm:WebResource - the web resource that is the digital

representation One digitization of the music score

• ore:Aggregation - the aggregation that groups the classes together • Four contextual classes:

• edm:Agent – who The creator of the work shown on the music score

• edm:Place – where • edm:TimeSpan - when • skos:Concept - what

The genre of the work shown on the music score

EDM classes enabling the description of cultural heritage objects

• Visualization of the three core classes

EDM classes - edm:ProvidedCHO

• The provided cultural heritage object (PCHO) is the cultural heritage object that you provide to Europeana

• A PCHO can be analog or digital born

• Examples of PCHOs related to sounds: a music score, a musical work, the broadcast of an interview on the radio, a nature sound, etc.

EDM classes - edm:ProvidedCHO

• The edm:ProvidedCHO class includes descriptive metadata properties applying to the PCHO: title, description, contributor (literal or reference), creator (literal or reference), format (literal or reference), type of object (literal or reference), etc.

• Most of the properties available in the edm:ProvidedCHO class are Dublin Core properties; some EDM properties are also available

• The edm:ProvidedCHO class has as an identifier the identifier of the PCHO you provide to Europeana: this value needs to be unique and persistent!

EDM classes - edm:ProvidedCHO

• A few examples of additional properties for edm:ProvidedCHO specified by the EDM profile for sounds

• ebucore:hasGenre (subproperty of dc:subject) to capture the genre of a resource

• ebucore:duration (subproperty of dcterms:extent) to capture duration information

EDM classes - edm:ProvidedCHO<edm:ProvidedCHO rdf:about="/2022104/urn_axmedis_00000_obj_55845aa3_2689_4fc9_95c1_2162a1ac7df7"> <dc:creator xml:lang="fr">Le Cifas - Centre inernational de formation en arts du spectacle, La Bellone - Maison du Spectacle à Bruxelles.</dc:creator> <dc:description xml:lang="fr">Enregistrement du Colloque et de la Table ronde "L'Apocalypse ici et maintenant", donné le Vendredi 6 juin 2008 à La Bellne, Maison du Spectacle à Bruxelles. Organisation : Cifas. En coréalisation avec La Bellone.</dc:description> <dc:description xml:lang="fr"> Effondrement des idéologies, catastrophes naturelles et technologiques, épidémies et famines, négation des valeurs morales et extrémismes font partie de notre actualité quotidienne. Nos sources d’énergie s’épuisent, la planète se réchauffe : la peur de l’avenir se répand. Nous nous intéressons aux échos et retombées que trouvent ces questionnements sur la scène contemporaine. L’interrogation sur l’Apocalypse, sur la «fin des temps » comme moment, acte et réalités en tant que thématique du théâtre contemporain sera donc au centre de cette journée d’étude qui proposera un aperçu et un état des lieux – aléatoire et subjectif – de l’Apocalypse sur la scène théâtrale contemporaine à travers écritures, mises en scène et esthétiques. </dc:description> <dc:language xml:lang="fr">fr</dc:language> <dc:title xml:lang="fr">L'Apocalypse ici et maintenant - 14</dc:title> <dc:type xml:lang="fr">audio</dc:type> <dc:type rdf:resource="http://www.eclap.eu/Classification/PerformingArtsType/501"/> <dcterms:extent>00:10:01.0</dcterms:extent> <dcterms:temporal rdf:resource="http://www.eclap.eu/Classification/HistoricalPeriod/566"/> <dcterms:temporal rdf:resource="http://www.eclap.eu/Classification/HistoricalPeriod/675"/> <edm:type>SOUND</edm:type> </edm:ProvideCHO>

EDM classes - edm:WebResource

• A web resource is a digital representation of the PCHO you provide to Europeana

• A web resource can be a link to a downloadable file (direct link) or a link to a web page showing the PCHO in context on your website

• Examples of web resources related to sounds: one digitization of a music score, a recording of a musical work, a link to a page showing a stream of the broadcast of an interview on the radio with additional context data, a recording of a nature sound, etc.

EDM classes - edm:WebResource

• The edm:WebResource class is not mandatory: the links to digital representations can be provided only as single links in the ore:Aggregation class

• The edm:WebResource class includes descriptive metadata properties applying to the digital representation: description, creator (literal or reference), format (literal or reference), specific rights

• Most of the properties available in the edm:WebResource class are Dublin Core properties; some EDM properties - especially edm:rights - are also available

• The edm:WebResource class has as an identifier the URL where the digital representation can be accessed: this value needs to be persistent!

EDM classes - edm:WebResource

• An example of additional properties for edm:ProvidedCHO specified by the EDM profile for sounds:

• Technical metadata about the digital representation ebucore:hasAudioEncodingFormatebucore:bitrate, ebucore:audioTrackConfiguration, ebucore:audioChannelNumber,ebucore:hasMimeType, ebucore:fileSize, ebucore:sampleRate, ebucore:sampleSize

EDM classes - edm:WebResource

<edm:WebResource rdf:about="http://biocase.zfmk.de/sounds?guid=BIAVCIFAFATI-GRATHYM005C001A20110421T051501-S015291E035753ID1-q9c9e9f9F.mp3"> <dc:description>O. Jahn (Creator)</dc:description> <dc:description>Recorder: Song Meter SM2, Firmware v.2.3.0; Microphone: SMX-II Microphones; Tape no.: ; Filter: edited and/or filtered</dc:description> <dc:format>audio/mpeg</dc:format> <dcterms:created>2011-04-21</dcterms:created> <edm:rights rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/"/> </edm:WebResource>

is a edm:WebResource class for

EDM classes - ore:Aggregation

• The aggregation links the digital representations (web resources) and the PCHO together in a bundle

• In other words: the ore:Aggregation class is the class that groups the other classes together

• The ore:Aggregation class references the links provided as digital representations of the PCHO (edm:isShownBy, edm:isShownAt, edm:object, edm:hasView)

• The ore:Aggregation class includes metadata properties that apply to both the PCHO and the web resources:

• edm:dataProvider and edm:Provider • edm:rights

• The ore:Aggregation class has its own identifier; this value also needs to be unique and persistent!

EDM classes - ore:Aggregation

<ore:Aggregation df:about="http://web-openup.nhm.ac.uk/oai-provider/index.php?form=display&amp;oaiid=ZFMKAMIBIO:ZFMK:GERMANY/ZFMKAMIBIO17&amp;db=0"> <edm:aggregatedCHO rdf:resource="/11618/_ZFMKAMIBIO_ZFMK_GERMANY_17"/> <edm:dataProvider>Zoological Research Museum Koenig</edm:dataProvider> <edm:isShownAt rdf:resource="http://orthoptera.speciesfile.org/Common/Basic/Taxa.aspx?TaxonNameID=0"/> <edm:isShownBy rdf:resource="http://biocase.zfmk.de/sounds?guid=BIAVCIFAFATI-GRATHYM005C001A20110421T051501-S015291E035753ID1-q9c9e9f9F.mp3"/> <edm:provider>OpenUp!</edm:provider> <edm:rights rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/"/> </ore:Aggregation>

EDM classes - edm:Collection

• The edm:Collection class is part of the EDM sounds profile and is not implemented in the current version of EDM

• A collection gathers different items of similar importance which relate to the main collection entity as its members

• The edm:Collection class is a sub class of the edm:ProvidedCHO class and is referenced in the ore:Aggregation class (see following slide)

• All properties of the edm:Collection class are specified in the Task force report

EDM classes - how is everything linked?<edm:WebResource rdf:about="http://biocase.zfmk.de/sounds?guid=BIAVCIFAFATI-GRATHYM005C001A20110421T051501-S015291E035753ID1-q9c9e9f9F.mp3"> <dc:description>O. Jahn (Creator)</dc:description> <dc:description>Recorder: Song Meter SM2, Firmware v.2.3.0; Microphone: SMX-II Microphones; Tape no.: ; Filter: edited and/or filtered</dc:description> <dc:format>audio/mpeg</dc:format> <dcterms:created>2011-04-21</dcterms:created> <edm:rights rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/"/> </edm:WebResource> <ore:Aggregation xmlns:ore="http://www.openarchives.org/ore/terms/" rdf:about="http://web-openup.nhm.ac.uk/oai-provider/index.php?form=display&amp;oaiid=ZFMKAMIBIO:ZFMK:GERMANY/ZFMKAMIBIO17&amp;db=0"> <edm:aggregatedCHO rdf:resource="/11618/_ZFMKAMIBIO_ZFMK_GERMANY_17"/> <edm:dataProvider>Zoological Research Museum Koenig</edm:dataProvider> <edm:isShownAt rdf:resource="http://orthoptera.speciesfile.org/Common/Basic/Taxa.aspx?TaxonNameID=0"/> <edm:isShownBy rdf:resource="http://biocase.zfmk.de/sounds?guid=BIAVCIFAFATI-GRATHYM005C001A20110421T051501-S015291E035753ID1-q9c9e9f9F.mp3"/> <edm:provider>OpenUp!</edm:provider> <edm:rights rdf:resource="http://creativecommons.org/licenses/by-sa/4.0/"/> </ore:Aggregation> <edm:ProvidedCHO rdf:about="/11618/_ZFMKAMIBIO_ZFMK_GERMANY_17"> <dc:identifier xmlns:dc="http://purl.org/dc/elements/1.1/">ZFMK - AMIBIO - 17</dc:identifier> <dc:relation xmlns:dc="http://purl.org/dc/elements/1.1/">http://www.biodiversitylibrary.org/name/Falco__tinnunculus</dc:relation> <dc:title xmlns:dc="http://purl.org/dc/elements/1.1/">Falco tinnunculus</dc:title> <dc:type>SoundRecording</dc:type> <edm:hasType rdf:resource="http://rs.tdwg.org/dwc/dwctype/SoundRecording"/> <edm:type>SOUND</edm:type> </edm:ProvidedCHO>

EDM classes - edm:Agent

• Why contextual classes? • A possible value in the edm:ProvidedCHO class for a music

work: • dc:creator: Wolfgang Amadeus Mozart

• You want to increase searchability and retrievability of your item and you have more than this to provide!

• dc:creator: Βόλφγκανγκ Αµαντέους Μότσαρτ, etc • edm:dateOfBirth: 1765 / edm:dateOfDeath: 1791

• This additional data is related to a person and can be modeled in EDM using the edm:Agent class

EDM classes - edm:Agent

• How to create contextual classes? • In the edm:ProvidedCHO class, map the identifier/reference

(URI) of the Agent as described in an ontology • dc:creator: http://viaf.org/viaf/32197206

• Map in an edm:Agent class all the data you have available from that ontology and use as an identifier for this edm:Agent instance the URI written below

• dc:creator preferred name in French: Wolfgang Amadeus Mozart

• dc:creator preferred name in Greek: Βόλφγκανγκ Αµαντέους Μότσαρτ

• edm:dateOfBirth: 1765 / edm:dateOfDeath: 1791

EDM classes - skos:Concept

Concepts - skos:Concept class • Subjects, types, genres can be represented • Multilingual labels (skos:prefLabel, skos:altLabel) can be provided

with their language • Editorial notes on a subject can be specified

Europeana Sounds vocabularies: • EuropeanaMusicGenre/FormVocabulary • EuropeanaNon-MusicGenre/FormVocabulary • Linked to the edm:ProvidedCHO class through ebucore:hasGenre

• Europeana Carrier Types Vocabulary

• Linked to the edm:ProvidedCHO class through dcterms:medium

EDM classes - edm:Place

Places - edm:Place class • Place of creation, place of curation, place related to the object

(place where a musical work was recorded, etc), place related to the creator of an object (place where the creator of a work was born, etc) can be represented

• Multilingual labels (skos:prefLabel, skos:altLabel) can be provided with their language

• Geo-coordinates can be added

EDM classes - edm:TimeSpan

Time - em:TimeSpan class • Date of creation, date of publication, date of recording can be

represented • Data ranges can be provided for a specific date to increase

retrievability

EDM classes - how is everything linked?<edm:ProvidedCHO rdf:about="http://data.europeana.eu/proxy/provider/2024913/photography_ProvidedCHO_Parisienne_de_Photographie_988_5"> ... <dc:description xml:lang="fr">Jean Cocteau (1889-1963), écrivain français, 1934. </dc:description> <dc:description xml:lang="en">Jean Cocteau (1889-1963), French writer, 1934. </dc:description> <dc:format rdf:resource="http://bib.arts.kuleuven.be/photoVocabulary/12003"/> <dc:identifier>988-5</dc:identifier> <dc:rights>© Boris Lipnitzki / Roger Viollet</dc:rights> <dc:subject rdf:resource="http://bib.arts.kuleuven.be/photoVocabulary/30114"/> <dc:subject xml:lang="fr">Film</dc:subject> <dc:subject xml:lang="fr">Artiste</dc:subject> <dc:subject xml:lang="fr">Portrait</dc:subject> <dc:title xml:lang="fr">Jean Cocteau (1889-1963), écrivain français</dc:title> ... <edm:type>IMAGE</edm:type> </edm:ProvidedCHO> <skos:Concept rdf:about=« http://bib.arts.kuleuven.be/photoVocabulary/30114"> <skos:prefLabel xml:lang="pl">teatr</skos:prefLabel> <skos:prefLabel xml:lang="nl">Theater</skos:prefLabel> <skos:prefLabel xml:lang="bg">театър</skos:prefLabel> <skos:prefLabel xml:lang="fr">Théâtre</skos:prefLabel> <skos:prefLabel xml:lang="uk">Театр</skos:prefLabel> <skos:prefLabel xml:lang="ru">Театр</skos:prefLabel> <skos:prefLabel xml:lang="ca">teatre</skos:prefLabel> <skos:prefLabel xml:lang="zh">剧场</skos:prefLabel> <skos:altLabel xml:lang="de">Schauspielhaus</skos:altLabel> <skos:altLabel xml:lang=« de">Sprech-Bühne</skos:altLabel> ... <skos:broader rdf:resource="http://bib.arts.kuleuven.be/photoVocabulary/30273"/> </skos:Concept>

EDM modeling - how can I represent a cultural heritage object using EDM?

• Thumbnails and Sound cultural heritage objects • Recommended but not mandatory; no logo or default thumbnails can be provided

EDM modeling - how can I represent a cultural heritage object using EDM?

• Thumbnails and Sound cultural heritage objects • Recommended but not mandatory; no logo or default thumbnails can be

provided

<ore:Aggregation rdf:about="#Aggregation"> <edm:aggregatedCHO rdf:resource="#PCHO"/> <edm:dataProvider>Sächsische Landesbibliothek - Staats- und Universitätsbibliothek Dresden</edm:dataProvider>

<edm:isShownBy rdf:resource="http://media.slub-dresden.de/fon/snp/b/006697/fon_snp_b_006697_01.mp3"/>

<edm:object rdf:resource="http://media.slub-dresden.de/fon/snp/b/006697/fon_snp_b_006697_01.jpg"/> <edm:provider>Deutsche Digitale Bibliothek</edm:provider> <edm:rights rdf:resource="#rights"/> </ore:Aggregation>

EDM modeling - how can I represent a cultural heritage object using EDM?Multiple web resources

EDM modeling - how can I represent a cultural heritage object using EDM?

<edm:WebResource rdf:about="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023441.jpg"> <edm:rights rdf:resource="#rights"/> </edm:WebResource> <edm:WebResource rdf:about="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023435.jpg">

<edm:rights rdf:resource="#rights"/> </edm:WebResource> <edm:WebResource rdf:about="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023436.jpg"> </edm:WebResource> <edm:WebResource rdf:about="http://www.mimo-db.eu/media/CM/AUDIO/CM0161358eCOAU900095301_01.mp3"> <edm:rights rdf:resource="#rights"/> </edm:WebResource> <edm:WebResource rdf:about=http://www.mimo-db.eu/media/CM/IMAGE/CMIM000015229.jpg"> </edm:WebResource>

<ore:Aggregation rdf:about="#Aggregation"> <edm:aggregatedCHO rdf:resource="#PCHO"/> <edm:dataProvider>DataProvider</edm:dataProvider>

<edm:isShownBy rdf:resource=http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023435.jpg"/> <edm:hasView rdf:resource="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023436.jpg"/> <edm:hasView rdf:resource="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000015229.jpg"/> <edm:hasView rdf:resource="http://www.mimo-db.eu/media/CM/AUDIO/CM0161358eCOAU900095301_01.mp3"/> <edm:object rdf:resource="http://www.mimo-db.eu/media/CM/IMAGE/CMIM000023441.jpg"/> <edm:provider>Provider</edm:provider> <edm:rights rdf:resource="#defaultRights"/> </ore:Aggregation>

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

• Connections can be created between cultural heritage objects as well as between a cultural heritage object and a web resource

• PCHOs can be related: • within a sequence • within a hierarchy

• Example: an opera in three acts, one PCHO is the opera itself and each act is also a PCHO related to the opera via a hierarchy, the three acts also connected and form a sequence

• Web resources can also be related: • within a sequence • within a hierarchy

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

<edm:ProvideCHO rdf:about="/9200300/BibliographicResource_3000051866016"> <dc:title>Wiener Zeitung - 1855-10-19</dc:title> <dcterms:isPartOf rdf:resource="/9200300/BibliographicResource_3000052917527"/>

… </edm:ProvideCHO>

<edm:ProvideCHO rdf:about="/9200300/BibliographicResource_3000052917527"> <dc:title>Wiener Zeitung</dc:title> <dcterms:hasPart rdf:resource="/9200300/BibliographicResource_3000051866016"/>

… </edm:ProvideCHO>

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

• Granularity of description and data propagation: you need to decide what you will provide to Europeana as PCHO

• How can the decision be made: • Do I have enough data to represent an artifact as a cultural

heritage object? • What would be useful to the end user? How do I want my

collection to be best discovered?

EDM modeling - how can I represent several cultural heritage objects and their relations using EDM?

• Multiple edm:WebResource instances instead of one PCHO per page

EDM and data quality

EDM data quality - what minimal set of properties is required?

Applicable class Mandatory Properties (or alternatives)Aggregation edm:dataProvider

Aggregation edm:isShownAt or edm:isShownBy

Aggregation edm:providerAggregation edm:rights Aggregation edm:aggregatedCHOAggregation edm:ugc (when applicable)

ProvidedCHO dc:title or dc:descriptionProvidedCHO dc:language for text objects

ProvidedCHO dc:subject or dc:type or dc:coverage or dcterms:spatial

ProvidedCHO edm:type

EDM data quality - what does the minimum look like?

EDM data quality - Recommended properties for Europeana Sounds

• The manual for data providers specifies for the project recommendations for properties to increase the quality of your submitted data:

https://docs.google.com/document/d/1cWbRS_hsEpEZXtCD-Z1Ljq2rK9Q_PUG0WMD7Wt2tHi0/edit

• The EDM profile for sounds established ebucore:hasGenre as a mandatory property

EDM data quality - what do we mean by richer data?

• Depth of description in provided metadata: presence, quality and consistency of meaningful elements

EDM data quality - what do we mean by richer data?

• High quality digital representations and appropriate rights statements, if possible the digital objects are freely re-usable

43

EDM data quality - what do we mean by richer data?

• Multilingual linked data, rich contextual information improving discoverability

Questions?

Let’s get practical! Agenda for day 2: Mint and mapping your records to EDM

Thank you!

Cécile Devarenne

cecile.devarenne@europeana.eu or content@europeana.eu