wiki:Taskforces/CMDI/Meeting20200212

CMDI general meeting 2020-02-12


  • What?
    • Report by specific task forces on completed and ongoing activities and strategy/planning for ongoing and upcoming tasks
  • Who?
    • Those involved or interested in the ongoing and upcoming tasks of the specific CMDI task forces
    • Wednesday 12 February 2020, 14:00 - 15:00 CET (on basis of doodle)
  • Where?

Documents

Preparation

  • Specific task force members: prepare report

Agenda

(Tentative)

  1. Reports
    1. Completed and ongoing tasks
      1. Common use cases evaluation (Andreas, ...)
      2. CMDI core components and profiles + extensions (Twan, ...)
      3. Use of FAIR vocabularies in CLARIN metadata (Twan, ...)
        • See above
      4. CMDI general documentation rewrite (Dieter, ...)
    2. Other CMDI related activities
      1. CMDI infrastructure developments
      2. Ongoing curation activities
      3. Support and other CMDI user aspects
  2. Planning and strategy
    1. Ongoing and upcoming tasks
      1. Continuation of work on core components and profiles, extensions and vocabularies as started?
      2. Solutions for gathering user feedback/experience/satisfaction (Alex, ...)
    2. Adaptations to strategy?
    3. Next meeting

Notes

Reports

Completed and ongoing tasks

  • Common use cases evaluation
    • Andreas: results summarised in sheet and report
    • Main outcomes: some consensus can be perceived, to some extent on the general level and a bit more on the resource type/genre specific level
    • Will serve as input for design of core components
  • CMDI core components and profiles, use of FAIR vocabularies
    • Task definitions can be sharpened a little bit further
    • Content of sheets (three tabs of spreadsheet document) needs to be further extended
    • Penny, regarding mandatoriness: some fields can/should be mandatory but allow for 'unspecified/unknown' to support legacy metadata and conversions
    • Philipp: also consider recommended status (cf DataCite)
    • Next steps:
      • add more aspects and vocabularies to the sheet (also taking into account repositories and associated standards like CLARIN D-Space, META-SHARE, Dataverse and the common use case evaluation)
        • [ ] TODO (task participants): review aspects and vocabularies from the angles mentioned above
      • for concrete use cases (probably best to start with fairly generic ones), work out details of incorporated aspects and implement them as core components
        • [ ] TODO (task participants): define requirements for 'pilot' use case
  • CMDI general documentation rewrite (clarin.eu/cmdi)
    • No work has been done towards this, although improvements are considered to be needed urgently.
    • Dieter cannot invest a lot of time and effort but volunteers to be the pacemaker

Other CMDI related activities

  • VLO 4.8 released
  • VLO 4.9 milestone determined (to be released April/May)
  • Design and requirements work for VLO 5.0 have started; there can be synergy or mutual influence and reinforcement between this and the CMDI activities

Planning

Ongoing & upcoming tasks

  • CMDI core components and profiles, use of FAIR vocabularies
    • Proceed as described above
  • Solutions for gathering user feedback/experience/satisfaction
    • This is mainly about facilitating interaction with and anong our end users
    • A central CLARIN blog or news(flash) item about this could be helpful

Upcoming meetings

  • CMDI core/vocabs: late February/early March
  • General meeting: before centre meeting (mid - late March)
Last modified 4 years ago Last modified on 02/12/20 16:05:03