Joint CMDI & Curation taskforces virtual meeting 2019-03-05

---

• What?
  • CMDI best practices
  • Common uses cases document
  • Recommend components
• Who?
  • Members of the CMDI or the Curation taskforces and other people involved/interested in the specification of best practices for CMDI
• When?
  • Tuesday 5 March 2019, 14:00 - 16:00 CET (on basis of ​doodle)
• Where?
  • Zoom: ​https://clarin.zoom.us/j/534115968
  • Note: If using Zoom for the first time, allow for some setup time before the meeting. The above link should get you started. See ​documentation for more information.

Documents

• ​CMDI Best Pratices draft on Overleaf (read link)
• Best Practices editing guide
• ​Common use cases (Google Doc; draft)
• ​Proposal for a recommended general info profile (Google Doc; work in progress)

Preparation

See notes of previous meeting

Agenda

(Tentative)

• Best practices
  • Actions last meeting
    • Guide
      • [X] Document CMDValidate markers in 'how to use section' (Menzo)
      • [\] Work on splitting up CS3 (Menzo)
        • started working on splitting CS3 into 2 BPs (use English for “core metadata” (CS7), and always specify the language used (CS3)) … still a bit work in progress
      • [X] Transfer 'principal responsible' information from GitBook to document; indicate with annotation like comments or TODOs but with new distinct styling (Twan)
        • See ​dda2994d
      • [ ] Align "Common approaches: Multilingual metadata" section with best pratices - in particular CS3 and its spin-off (Twan)
      • [x] Publish documentation for guide release process (Twan)
        • See Taskforces/CMDI/BestPracticesPublishing
      • [X] Add references to 'How to use this guide' on basic CMD principles and general web resources best practices (Menzo?)
      • [X] Write paragraph on common approaches part of guide in "Outline" (Alex)
      • [X] Make GitHub issues for "Check CMDI (instance) validator" TODOs (Twan)
        • See ​6b79d6ab
      • [x] Make GitHub issues for "requesting changes to existing components" (see C11) (Twan)
        • See ​https://github.com/clarin-eric/component-registry-front-end/issues/143 and ​5bc1c7ef
      • [X] Concepts section of component modelling: add reference to CCR registry, the metadata schema within it, and advice to look at concept definitions (Oddrun)
      • [x] Check coverage of CCR (concept selection, new concept request) in workflow (Susanne)
      • [\] Write "C16: Refer to approved concepts" (WHO?)
      • [\] Expand "P1: Reuse components" (Alex)

• Discussion of TODOs and notes in guide page i to 10

• Common uses cases document
  • Document: ​Draft as Google Doc
  • [x] Susanne finishes the ​web form for questionnaire and continues work on the document

• Recommend components
  • Report on ISO 24622-3 (recommended components) activities (Hanna)

• CCR
  • Report (the CCR coordinators)

• Vocabularies
  • Report (Menzo)

• Planning
  • ...
  • Next meeting

Notes

Best practices guide

Discussion of notes and TODOs

Remaining TODOs

• [ ] Align "Common approaches: Multilingual metadata" section with best pratices - in particular CS3 and its spin-off (Twan)
• [\] Write "C16: Refer to approved concepts" (Oddrun)

New TODOs

• [ ] Fix 'overfull' page headers (Andreas)
• [ ] Cover "B centre requirement" box in 'How to use the guide' section (Menzo)
• [ ] P1: create and reference Component Registry issue for recommended status property and filtering/display features (Twan)
• [ ] Review TODOs and work in progress on page 11-20

Action points

Common uses cases document

• [ ] Add more guidance to 'Information to present' part of ​questionnaire web form (Susanne, Andreas)

General info/recommended components

• Work goes on, looking at one metadata 'aspect' at a time. We're keeping an eye on compatibility with existing CMDI workflows (in particular mapping logic).

CCR

Coordinators are now looking at availability

Planning

Next meeting in the first week of April.

• Doodle: ​https://doodle.com/poll/k7gn8fkpmdbk8aqa