publication of europeana sounds data in europeana
TRANSCRIPT
Publication of Europeana Sounds data in Europeana
Cécile Devarenne Operations Officer
Metadata training, Europeana Sounds project Athens, 25th/26th of June 2015
Content✦ May and June publications in Europeana ✦ Organisation and processes in place ✦ About your data: feedback and quality
May and June publications in Europeana
First publications
✦ May publication: 26,620 sounds records successfully ingested and published into Europeana
✦ One query for the whole project: http://www.europeana.eu/portal/search.html?query=europeana_collectionName%3A20592*&rows=24&qt=false
✦ June publication: at the end of next week, 30,155 sounds records and 100 video records will be retrievable
First publication
Organisation and processes in place
New submissions
✦ If you have not submitted data to Europeana yet, make sure that your institution has signed the Data Exchange Agreement
✦ Publication in Mint ➡ EDM data exposed on Mint’s OAI-PMH server ➡ One dataset per data provider ➡ Data ready to be harvested by Europeana
✦ Publication in Europeana ➡ Europeana ingests, maps, enriches your data ➡ Feedback is sent ➡ The process takes in average a month
Updates and addition of records
✦ Improve quality for existing data: un-publish, update mapping and republish
✦ Ingesting more data: add new imports and publish them
✦ Your Europeana collection keeps growing and can regularly be updated on the Europeana portal
✦ Updates can be triggered every month at the latest on the 21st; the list of datasets to be ingested is sent by Tom.
Next round of publication
✦ Ingestion and publication of data will stop over summer and resume at the end of August
✦ Next submission deadline is the 21st of August ✦ Your data will be live around mid-September ✦ If you are willing to receive feedback before the
deadline, you can publish your data in Mint and inform Tom, we will be happy to get back to you :-)
About your data…
Monthly feedback
Numbers! Submitted vs published records
✦ Validation against the EDM schema: should not be an issue since a valid record in EDM for Sounds is also a valid record in EDM
✦ Importance of using persistent unique identifiers: these identifiers populate the rdf:about property of the ProvidedCHO class. If some identifiers are duplicated or missing, records will be discarded
Numbers! Submitted vs published records
✦ Count of records in Mint not necessarily based on the amount of ProvidedCHOs, it is based on what you choose as item level in the Define items screen
✦ Europeana publishes one records for each ProvidedCHO
✦ For instance: 21,058 records were published in Mint for the first delivery of RBB AIT DISMARC, out of which 23,128 distinct providedCHO generated 23,128 records in Europeana
Display! Mint preview and Europeana portal
✦ The Mint preview gives an idea of what your record will look like on the Europeana portal
✦ Europeana performs editings and enrichments on your provided data so the final display of your data in the Europeana portal will not be exactly the same as the Mint preview
Display! Mint preview
Display! Europeana portal
EDM for Sounds vs EDM
✦ You map your data to EDM for Sounds ✦ A crosswalk between EDM for Sounds and EDM
was created by Nikos and reviewed by Valentine ✦ Both your data in EDM for Sounds and EDM are
exposed in Mint’s OAI-PMH endpoint ✦ Europeana ingests the EDM version of your data ✦ No data is lost, but the specificity of some
properties is not emphasized on the portal
EDM for Sounds vs EDM
Crosswalk
✦ One google doc: https://docs.google.com/spreadsheets/d/1tx89FOizSSVuEOxnbuhkazCAbPqh6B7Sf7xaQyG_baQ/edit#gid=0
✦ D5.2: https://basecamp.com/1936492/projects/2141070/messages/43273630?enlarge=159279307#attachment_159279307
Thumbnails
✦ Using edm:object property ✦ It has to be a representation of the object you are
describing: should be unique, no logo will be accepted
✦ One exception: record covers
More feedback…
Feedback: general
✦ Presence of mandatory elements ✦ Meaningfulness of the data: special attention to
titles and descriptions ✦ Think of the end user: for instance, in properties
related to measurements, add the measurement units to make your data more understandable
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
Mandatory properties
Feedback: direct links and appropriate rights statements for digital objects
Feedback: direct links and appropriate rights statements for digital objects
Feedback: direct links and appropriate rights statements for digital objects
<ore:Aggregation rdf:about="http://mint-projects.image.ntua.gr/data/sounds/Aggregation_http://epth.sfm.gr/card.aspx?mid=1977"> <edm:aggregatedCHO rdf:resource=«…»/> <edm:dataProvider>Music Library of Greece of The Friends of Music Society</edm:dataProvider> <edm:hasView rdf:resource="http://epth.sfm.gr/media/Thraki/Song/tc319_15.rtf"/> <edm:hasView rdf:resource="http://epth.sfm.gr/media/Thraki/Foto/e010719.jpg"/> <edm:hasView rdf:resource="http://epth.sfm.gr/media/Thraki/Foto/e010721.jpg"/> <edm:hasView rdf:resource="http://epth.sfm.gr/media/Thraki/Foto/e010812.jpg"/> <edm:isShownBy rdf:resource="http://epth.sfm.gr/media/Thraki/Sound/tc319_15.mp3"/> <edm:provider>Europeana Sounds</edm:provider> <edm:rights rdf:resource="http://creativecommons.org/licenses/by-nc/4.0/"/> </ore:Aggregation>
Feedback: connections and collections
✦ Important part of the feedback is focused on connections between classes and identifiers in general: ✦ The aggregatedCHO rdf:resource property must
be filled in with the same URI as the rdf:about of the providedCHO: this is predefined in Mint
✦ The web resources classes must have as rdf:about the URL of one of edm:object, edm:isShownAt, edm:isShownBy or edm:hasView
Feedback: connections and collections <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&oaiid=ZFMKAMIBIO:ZFMK:GERMANY/ZFMKAMIBIO17&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>
Feedback: connections and collections
✦ How to model collections? ✦ How to model hierarchies and links between your
objects? ✦ To be reviewed in more details tomorrow, feel free
to ask us questions :-)
Enrich your data with specific Sounds vocabularies (In Mint)
✦ ebucore:hasGenre needs to be populated with concepts from the Sounds Genre vocabulary
➡See the manual for data providers and Mint documentation
➡Please try to choose the most specific entries possible: conditional mappings as presented tomorrow will help
✦dcterms:medium can be populated with concepts from the RDA Carrier Type vocabulary
Enrich your data with specific Sounds vocabularies
✦ The Dismarc vocabularies were mapped in Europeana tools and a link from Dismarc genre or format vocabularies in your data can be dereferenced
➡ http://purl.org/dismarc/ns/dmFormats/80001000 ➡ http://purl.org/dismarc/ns/dmGenres/13001
✦ Other vocabularies ➡ You can also include links to other standardized
ontologies such as MIMO musical instruments, MIMO instrument makers, Viaf, Geonames, Gnd, IconClass, AAT
➡ If you use local vocabularies, please create contextual classes in EDM for sounds
Enrich your data with specific Sounds vocabularies
✦This will be of major importance for presenting your data in the Music channel
✦Further work on Sounds specific vocabularies (choice of appropriate ontologies for your material, multilingual translations, etc) can be achieved by WP1
Guidance and help
Guidance and help Europeana Professional:http://pro.europeana.eu/provide-dataContent inbox – for all ingestion & metadata related matters [email protected]
Questions?
Thank you!
Cécile Devarenne