wiki:Taskforces/CMDI/Meeting20190111

Joint CMDI & Curation taskforces virtual meeting 2019-01-11


  • What?
    • CMDI 1.2 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?
    • Friday 11 January 2019, 10:00 - 12:00 CET (on basis of doodle)
  • Where?

Documents

Preparation

See notes of previous meeting

Agenda

(Tentative)

  • Best practices
    • Actions last meeting
      • Guide
        • [] CMDValidate markers have to be rendered nicely, and this has to be indicated in the 'how to use' section (Menzo)
        • [x] Smells section on p.24 should get a page reference to p.13 where smells are introduced (Twan -> ​dccdf8)
        • [ ] Fix namespaces table rendering (e.g. rotated on separated page; TODO: Alex)
        • [X] Add bibliography section (TODO: Menzo)
        • [x] Contributions and acknowledgements section has to be created (Twan -> f33173)
        • [ ] Publish new version of guide (Twan)
    • Work on guide
    • Guide release
  • Recommend components
    • Status?
    • ISO 24622-3 call on 2019-01-18
      • Maria Gavriilidou: "In order to coordinate the work concerning the recommended profiles and components for Part 3 of ISO 24622, and to start discussing the scope and methodology of our endeavor, I have set up a doodle poll with several dates and several time slots per day. Please indicate your preferences here https://doodle.com/poll/gqwsip5crrgup32c. If you think more people should participate, please indicate their names and emails so that I can send them the poll."
  • CCR
  • Vocabularies
    • Actions last meeting
      • [] Resource types: propose current vocabulary to centre committee (Curation TF - Matej?)
      • [] Licences: Menzo can convert current state of spreadsheet to vocab
      • [] Licences: Exact modelling of vocabulary requires thought/discussion (use of collections and/or various concept schemes and broader/narrower for licence families and licences). Start discussion with curation task force to get this going
  • Planning

Notes

Best practices guide

Based on comments and TODOs in the text

  • We use British English (spelling) conventions
  • CS3 (Explicitly name the languages used)
    • Decided to split this up: (1) use (also) English and (2) specify used language
    • We don't use default language?
    • Always provide English description
    • Title can often be translated or embedded in English but translation is not mandatory, sometimes not desirable
    • Add a smell for content marked English (or no language specified?) that use non-ASCII characters?
  • CS4 (Use specific rather than (only) generic metadata)
    • Conflates generic/specific and within-field value concatenation; to be split up
  • Common approaches
    • Multilingual metadata: Guidelines for translating e.g. titles to English

Changes in tex project made during and in preparation of this meeting: see commit 86deac6d.

TODOs:

  • For ALL:
    • Go through document and prepare to discuss open TODOs (orange boxes)
  • [ ] Document CMDValidate markers in 'how to use section' (Menzo)
  • [ ] Fix namespaces table (~p15) rendering, e.g. rotated on separated page (Alex)
  • [ ] Complete/finetune bibliography (Menzo)
    • [ ] Add references throughout document
    • [ ] Handle for CMDI 1.2 ref
  • Work on splitting up CS3 (Menzo)
  • [ ] Go through document and check British English spelling (Oddrun)
  • [ ] Transfer 'principal responsible' information from GitBook? to document; indicate with annotation like comments or TODOs but with new distinct styling (Twan)
  • [ ] Align "Common approaches: Multilingual metadata" section with best pratices - in particular CS3 and its spin-off (Twan)
  • [ ] Release new version of guide (Twan, Menzo, Alex)
    • Blockers: namespace table rendering and bibliography tuning
  • [ ] Create documentation for guide release process (Twan)

Common uses cases document

  • draft as Google Doc newly shared by Susanne
  • Number of use case topics gathered along various dimensions: resource type, genre/theme, age
  • Plan for now is to find one or two experts for a number of the use cases and ask these experts to describe their use case on basis of a template (to be created)

TODOs:

  • [ ] Add any information and ideas you may have including names of experts to the doc (ALL)
  • [ ] Make template for gathering case study input (Susanne)

General info / recommended components

  • ISO 24622-3 call on 2019-01-18
    • Will be attended by Hanna, Menzo, Twan, (...?)
  • CLARIN internal meeting with invitees such as Felix (see planning)

Vocabularies

Nothing to discuss. Actions remain open (from previous meeting):

  • [ ] Resource types: propose current vocabulary to centre committee (Curation TF - Matej?)
  • [ ] Licences: Menzo can convert current state of spreadsheet to vocab (Menzo)
  • [ ] Licences: Exact modelling of vocabulary requires thought/discussion (use of collections and/or various concept schemes and broader/narrower for licence families and licences). Start discussion with curation task force to get this going

Curation

Ongoing efforts on modality facet mapping (2018-12-06 meeting)

Planning

  • Next best practices meeting in wk6 or wk7 (4-15 February)
  • ISO 24622-3 call on 2019-01-18 (for those invited)
  • CLARIN internal meeting on general info, recommended components: (early) February
    • TODO Hanna: [ ] Doodle
  • Meeting with focus on curation/vocabularies (requires attendence from Matej)
    • TODO ???: [ ] schedule and prepare meeting
Last modified 5 years ago Last modified on 05/20/19 13:59:23