| 42 | |
| 43 | Present: Alexander, Andreas, Dieter, Felix, Neeme, Matej, Oddrun, Thomas, Twan |
| 44 | |
| 45 | === Two task forces situation === |
| 46 | ("one task force, two systems?") |
| 47 | |
| 48 | * proposal to merge these into one 'expert group' and branch off into task forces with limited 'mission' and temporal scope |
| 49 | * Note TG: there could also be more long-lived task forces such as standard/model group |
| 50 | * migrate to single mailing lists |
| 51 | * freeze curation TF list? Save for future curation activities? |
| 52 | * new list for CMDI expert/interest group? |
| 53 | |
| 54 | === CMDI strategy === |
| 55 | |
| 56 | See [https://docs.google.com/document/d/1cRJKiise8HFS16gqG4gC3TsI0W-TnLSnebh_YS6mZ3U/edit?usp=sharing strategy document]. |
| 57 | |
| 58 | 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. |
| 59 | |
| 60 | * Analysis section |
| 61 | * Some recent and ongoing tasks were to be added to the table |
| 62 | * SWOT analysis |
| 63 | * some strengths, weaknesses, threats added / adapted |
| 64 | * observation: most weaknesses are flip-side of strengths: powerful but complex model, (too) much flexibility, allowing modelling means supporting modelling... |
| 65 | * Goals |
| 66 | * Should be motivated by |
| 67 | * SWOT analysis |
| 68 | * Input from users |
| 69 | * 'Natural' use cases pop up in the shape of support requests for new metadata (Leiden, Belarus, ...) |
| 70 | * To some degree we are/represent users |
| 71 | * We also need to go out and talk to users (common use cases investigation is a great start) |
| 72 | * [ ] Homework: suggestions for goals |
| 73 | |
| 74 | === Tasks === |
| 75 | * There are still some open best practices TODOs (see [https://www.overleaf.com/read/wfsggvdjbbgj Overleaf]) |
| 76 | * Some high priority ones could be continued to be worked on by those interested (parallel task) |
| 77 | * Common use cases questionnaire |
| 78 | * Andreas has streamlined results into [https://docs.google.com/spreadsheets/d/1-GkqT3W1adp-dYL7OZr8IoYB8xgwbwD_8bf5SuPAJd0/edit?usp=sharing spreadsheet] (Google Sheets) |
| 79 | * there may be some test entries that have to be excluded |
| 80 | * []have a look at this |
| 81 | * Core metadata |
| 82 | * Should also include recommended components for use cases/resource classes |
| 83 | * See [https://docs.google.com/document/d/12xBfAzrBChY1HT-aQTzdcGv1yxtCgYpDxGZRNcqFmoc/edit?usp=sharing start of draft for proposal] (Google docs) |
| 84 | * Initial phase: general info? Some initial work has already been done. |
| 85 | * Vocabularies investigation |
| 86 | * Already started a bit by Daan, Dieter, Twan |
| 87 | * Can run in parallel to 'general info' task |
| 88 | |
| 89 | === Next meeting === |
| 90 | * Topics: |
| 91 | * organisation of task force |
| 92 | * strategy: goals and planning |
| 93 | * work on tasks |
| 94 | * Doodle: https://doodle.com/poll/k6xk7ka4bhywpyqk |