Joint CMDI & Curation taskforces virtual meeting 2019-10-28

---

• What?
  • Discussion on CMDI (task forces) strategy
• Who?
  • Members of the CMDI or the Curation taskforces and other people involved/interested in contributing to CMDI and metadata curation
  • Monday 28 October 2019, 14:00 - 15: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 strategy
• ​CMDI core metadata proposal

Preparation

See notes of previous meeting

Agenda

(Tentative)

1. Summary of discussion/conclusions from meeting at annual conference
2. State of CMDI and strategy considerations
   1. Review and expansion of ​CMDI strategy document
3. Tasks
   1. Documentation (incl Best Practices)
   2. Documentation of and support for (common) use cases (cf. ​Common Use Cases questionnaire and ​questionnaire responses)
   3. Core metadata
   4. Use of vocabularies
   5. Software stack development
   6. Metadata curation work
4. General task force(s) strategy/operation
   1. Areas of focus
   2. Task forces organisation
   3. Planning

Notes

Present: Alexander, Andreas, Dieter, Felix, Neeme, Matej, Oddrun, Thomas, Twan

Two task forces situation

("one task force, two systems?")

• proposal to merge these into one 'expert group' and branch off into task forces with limited 'mission' and temporal scope
  • Note TG: there could also be more long-lived task forces such as standard/model group
• migrate to single mailing lists
  • freeze curation TF list? Save for future curation activities?
  • new list for CMDI expert/interest group?

CMDI strategy

See ​strategy document.

It would be good to get 'formal' approval/mandate from the centre committee and in any case keep them updated about our activities but essentially we can determine most of the strategy.

• Analysis section
  • Some recent and ongoing tasks were to be added to the table
• SWOT analysis
  • some strengths, weaknesses, threats added / adapted
  • observation: most weaknesses are flip-side of strengths: powerful but complex model, (too) much flexibility, allowing modelling means supporting modelling...
• Goals
  • Should be motivated by
    • SWOT analysis
    • Input from users
      • 'Natural' use cases pop up in the shape of support requests for new metadata (Leiden, Belarus, ...)
      • To some degree we are/represent users
      • We also need to go out and talk to users (common use cases investigation is a great start)
  • [ ] Homework: suggestions for goals

Tasks

• There are still some open best practices TODOs (see ​Overleaf)
  • Some high priority ones could be continued to be worked on by those interested (parallel task)
• Common use cases questionnaire
  • Andreas has streamlined results into ​spreadsheet (Google Sheets)
    • there may be some test entries that have to be excluded
    • []have a look at this
• Core metadata
  • Should also include recommended components for use cases/resource classes
    • See ​start of draft for proposal (Google docs)
    • Initial phase: general info? Some initial work has already been done.
• Vocabularies investigation
  • Already started a bit by Daan, Dieter, Twan
  • Can run in parallel to 'general info' task

Next meeting

• Topics:
  • organisation of task force
  • strategy: goals and plan
  • work on tasks
• Doodle: ​https://doodle.com/poll/k6xk7ka4bhywpyqk