1 / 15

CMDI Interoperability Workshop

CMDI Interoperability Workshop. Daan Broeder TLA / MPI for Psycholinguistics CLARIN NL. Agenda Tuesday June 4. 12.15 - 13.00 Lunch 13.00 - 13-15 Welkom. Daan Broeder 13.15 - 13.45 Status CMDI, existing tools & framework. Twan Goosen

afric
Download Presentation

CMDI Interoperability Workshop

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. CMDI Interoperability Workshop Daan Broeder TLA / MPI forPsycholinguistics CLARIN NL

  2. Agenda Tuesday June 4 12.15 - 13.00 Lunch 13.00 - 13-15 Welkom. Daan Broeder 13.15 - 13.45 Status CMDI, existing tools & framework. TwanGoosen 13.45 - 14.00 CMDI Usage, profiles & components. Dieter van Uytvanck 14.00 - 14.30 Overview Meta-Share infrastructure. Penny Labropoulou & Maria Gavrilidou 14.30 - 15.00 Coffee 15.00 - 15.30 Challenges of metadata for LR interoperability and it costs, Koenraad de Smedt 15.30 - 15.45 Metadata quality and curation responsibility, MenzoWindhouwer, Dieter van Uytvanck 15.45 - 16.45 10-minute presentations on LR metadata interoperability • MatejDurco: from TEI to CMDI at ICLTT • Daan Broeder: from IMDI to CMDI • MenzoWindhouwer: from DC to CMDI at DANS • PavelStranek or Josef Misutka: META-SHARE to CMDI • Marta Villegas: hybrid solution for OLAC, CMDI, META-SHARE • LeneOffersgaard • ? 16.45 - 18.00 Discussion and possible next steps

  3. Wednesday June 5 • 10.00 - 13.00 Opportunity to discuss, exchange and work on metadata conversion tools. - Demo’s of Tools, Service - If simple available to CLARIN source code repository - Further subjects?

  4. Why this workshop? • Appeals from CLARIN participants that were also partners in META-SHARE • META-SHARE project finished, many LR MD records available also useful to the CLARIN community • CLARIN use for metadata without resources? • Thought useful to embed this in general question of metadata interoperability: TEI, DC/OLAC • How useful is the CMDI approach to accommodate other metadata schema? • Sustainability. What can the CMDI infrastructure offer in this respect? Organized by CLARIN NL / MPI-PL; main force behind the CMDI development and CMDI registry maintenance

  5. From IMDI to CMDI • TLA / MPI-PL has been an IMDI archive since 2000 • IMDI has its advantages: • Excellently suited for Multi-Modal/Multi-media resources • No confusion what schema to use • Tools specifically tailored for dealing with the IMDI schema • and its disadvantages • Limited applicability outside the core TLA domain • Limited flexibility (although there is support for profiles) • Moving from IMDI to CMDI also in our internal workflow necessary to support a larger variety of resources in the archive and be a full CLARIN A center and accept CMDI described data depositions. • However almost all tools: LAMUS (archive deposition), IMDI-Browser, IMDI-Search (archive exploitation) must be adapted • Will provide built-in upgrade IMDI-> CMDI e.g. Arbil, Lamus

  6. Three steps to heaven • Internal IMDI, external CMDI (OAI harvesting) • imdi2cmdi transformation • Specific ones for special IMDI profiles • Hybrid archive: internal IMDI & CMDI metadata records • CMDI records are directly accessible from outside and inside for new CMDI capable tools • Internal information systems consume IMDIfied CMDI via a cimdi2imdi transformation (with information loss!) • CMDI records need to be inserted in the archive by hand • CMDI archive: all metadata is in CMDI format • Requires adaptation of (almost) all tools

  7. TLA IMDI Archive OAI-PMH provider 2CLARIN IMDI Browser IMDI search IMDI2 CMDI IMDI DBs IMDI crawler LAMUS imdi MD imdi MD imdi MD TLA ARCHIVE imdi MD R R R R

  8. TLA Hybrid Archive OAI-PMH provider 2CLARIN IMDI Browser IMDI search IMDI2 CMDI IMDI DBs IMDI crawler CMDI2 IMDI LAMUS imdi MD CMDI MD CMDI MD imdi MD CMDI MD imdi MD imdi MD CMDI MD R R R R R R R TLA ARCHIVE

  9. TLA Hybrid Archive CMDI Browser IMDI Browser IMDI search CMDI search IMDI DBs IMDI crawler CMDI2 IMDI CMDI DBs LAMUS imdi MD CMDI MD CMDI LAMUS CMDI MD CMDI MD imdi MD imdi MD imdi MD CMDI MD

  10. Next Steps • CMDI standardization: ISO track • CMD model • CMDI implementation language • CMDI recommended components • Conversion/Generation tool repository/registry • Single profile solutions for generation HTML/PHP/XForm • Harvesting! • See what is there and how it looks: VLO, CMDI-Browser • Develop profile specific metadata visualization; stylesheets • Sustainability: XSLTs to upgrade, EUDAT SimpleStore, … • CMDI future workshop, Q4 2013, also on interoperability issues • CLARIN Taskforces to improve existing CMDI infra

  11. Contributions to CMDI Interop.

  12. Participants • TwanGoosen (MPI-PL) • MenzoWindhouwer (DANS) • MatejDurco (OEW • Lars Johanson (NBNO) • LeneOffersgaard (UCP) • Dieter van Uytvanck MPI-PL) • Mara Gavrilidou (ILSP) • Penny Labropoulou (ISLP • Koenraad de Smedt (UIB) • NeemeKakusk (UT) • JussiPiitulainen (CSC) • Martin Matthiesen (CSC) • OddrunOhren(NBNO) • Marta Villegas (UPF) • Thorsten Trippel (UTU) • OyrizdGeysdal (UIB) • Josef Misutka (UFAL) • PavelStranak (UFAL) • Marc Kemps-Snijders (MI) • Daan Broeder (MPI-PL)

  13. Conclusions • Good that we were able to talk about the interoperability issues • Clear that CMDI cannot exist on inteself but interoperability has to be actively pursued. • The CMDI trac and interop tool repository/pages will be a start.

More Related