1 / 12

Repository Registries

This document outlines the proceedings of a working group focused on integrating re3data and GocDB, aiming to improve metadata management for repository registries. It explores the current state of discussions, contributions from various entities, and highlights open questions around collection registries, federation metadata harmonization, and the need for clear classification. The session summarizes actions planned for the future, including the establishment of a Collection Registry working group and a Repository Registries working group to define schemas and exposure protocols.

porter
Télécharger la présentation

Repository Registries

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. Repository Registries Agenda

  2. State of theDiscussion • Short History: • P3BoF Linking re3data and DataBib • P5BoFWhatisneeded – a start • Contributions: re3data, gocdb, eudat, Biomed Regs • (nofurtherinfo on Biomedregsyet) • VM: agreement on classification and waytogo • lots of open questions • Docs, Schemas from CLARIN, Karmela • P6 Session Summarizing and Actions

  3. Wherearewe? Whatisspecial? Different MD? But thereis an urgent need! That‘swhatmany people do. Collection MD recordsare just asother MD records • Herewehavetwo • activities: • Re3data type • Federation type Lots of mapping and curation Curation responsibility

  4. Wherearewe? highly granular MD Collection MD Repository MD Federation MD • Open questions: • Whattobedonefor Collection Registry? • Whatto do toharmonizeFederation MD? • Where do weneedtodistinguish?

  5. Repository Registries - Classification

  6. Collection Registries Tobetaken care of byBob

  7. Joint Approach harvesting exposing re3data Schema Trustful Repository Re3data service harvesting extracting GocDB+ Schema Trustful Repository exposing GocDB+ service other Schema harvesting extracting Trustful Repository exposing Overlap in schemastobeused. Maketwoschemasrecommendations. Large Federation

  8. Large Federations Need toidentifythemtoparticipate in furtherelaborations. WG needstotake an activeroleand time 

  9. Relations 1 1 GocDB+ Schema Rep Registry Service Trustful Repository 3 2 4 5 Metadata Service Simplifiedinteraction: 1: harvestfederation type metadata 2: request all repsthatoffermetadata (probably of certain type) 3: returnlist incl. portspecs etc. 4: requestmetadatarecords 5: return all metadatarecords

  10. Re3Data Schema • descriptive • Controlled vocabulary aspects • usable for humans to find suitable repositories

  11. GOCDB Schema

  12. Next Steps • Let‘ssetup a ‚simple‘ RDA Collection Registry WG to • Quicklyspecifythe Collection Registry • Specifyfirstpartners and responsibilities • Develop and Implement Simple Software • Discusswith NDS and EUDATaboutservice • Chairs: Bob & Herman/SJT • Let‘ssetup a Repository Registries WG to • Definere3dataschemaas RDA recommendation • studyvariousfederationusecases • identifyoverlap in schemas • definefederationschemaas RDA recommendation • (GocDBseemstobe a candidatetostartfrom) • defineexposureprotocols and perhapssomemappings • Chairs: Peter/Johannes & ?

More Related