1 / 8

Data Archiving and Networked Services

Data Archiving and Networked Services. EASY Dublin Core and CMDI Georgi Khomeriki , Marnix van Berchum , Menzo Windhouwer CMDI Interoperability workshop Utrecht, 4 June 2013. EASY overview borrowed from Jan van Mansum. Separate OAI-PMH endpoint for CMDI.

abner
Download Presentation

Data Archiving and Networked Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data Archiving and Networked Services EASY Dublin Core and CMDIGeorgiKhomeriki, Marnix van Berchum, Menzo WindhouwerCMDI Interoperability workshop Utrecht, 4 June 2013

  2. EASY overview borrowed from Jan van Mansum

  3. Separate OAI-PMH endpoint for CMDI • Syncs with the ‘Niet-DC-metadata’ directory and offers the alternative metadata formats for harvesting • But also the EASY DC is offered (as required by OAI-PMH) • Completes the CMDI • Header • resolvable self link • Content • may fill the DANS-DC-Metadata component for collection level CMDI • skips currently resource proxies to individual files • EASY is data set oriented and doesn’t yet support PIDs for individual files • Target: in production later this week 

  4. DANS CMDI requirements(under construction) • For collection level accepts any CMDI profile that allows the DANS-DC-Metadata component • Can be optionally filled by the user to fill EASY at ingest • Can be filled from EASY during the sync • For this the position of DANS-DC-Metadata should be known, i.e., it must always be the last optional component in the profile • Resource specific CMDI can use any profile • Place collection and resource CMDI in the ‘Niet-DC-Metadata/CMDI’ directory in the dataset

  5. Thank you for your attention For more information please contact Menzo.Windhouwer@dans.knaw.nl

More Related