60 likes | 70 Views
Summary of current challenges in exchanging digital content between repository platforms and proposed solutions to improve interoperability and data sharing. Includes use cases, state-of-the-art analysis, and recommendations for implementation. Expected impacts and feedback desired for further development.
E N D
Research Data Repository Interoperability WGDavid Wilcox, Thomas JejkalMontreal, 09/20/17 www.rd-alliance.org - @resdatall CC BY-SA 4.0
Summary of the Problem • Exchange of digital content between repository platforms is challenging • Different data models, metadata, semantics, interfaces • Current state of the art (e.g. Dublin Core, OAI-PMH, SWORD) well adopted but very limited • Upcoming approaches (e.g. Linked Data Platform, Resource Sync, OAI-ORE) supported by a comparable small subset of platforms • Some varied use cases: migration, replication, cross-domain sharing • Migration between same platform, but different version • Replication between different locations • Share with domain and cross-domain scientists
Status of the Deliverable • D1. Research Data Repository Interoperability Primer (M6) • Use Case description, state of the art and gap analysis • Foundation for further discussions • DOI: 10.15497/RDA00020 • D2. Interface Specification Draft (M12) • Will define no interface but adoptable recommendations • Active WG members agreed on BagIt-based approach • Recommend to follow the BagIt specification as far as possible • Recommend to include basic metadata in well-known standard schema, e.g. Datacite 4.0 • Recommend to provide machine readable profile information
Initial Adopters • First prototype implementation can start as soon as D2 is finished • Create first profile definition(s) for well-known packages • Fedora, DataONE, Data Conservancy, Research Object, DARIAH • Talk to developers of existing BagIt-based packaging solutions • Ask to include basic metadata • Create new / correct existing profile • Demonstrate at least one example migration/replication between two platforms
Expected Impact of the Deliverable • Recommendations that are comparably easy to adopt • Support for both state-of-the-art and legacy platforms • Provide users with a common tool to e.g. transport, exchange or backup their content • Basis for further agreements of package content to improve interpretability of package content
Feedback Desired from RDA Community From Platform Developers: • How do you assess the applicability for your platform? • Where do you see challenges/obstacles for an adoption? • Do you want to be an adopter? From Platform Users: • Do you think our approach will help you? • What do you think is missing?