Note:

• CEDAR will not be used (discussed 24-10-2023)

• Data Stewardship Wizard (DSW) could maybe be used (Suggestion Rob Hooft).

• Some of the scenarios mention the DSW, but this could be another tool as well. No choice has been made.

...

In my opinion it would make sense to have two main solutions. To stick with the Metroline Analogy: a Basic and an Advanced Track:

1. Basic Track - A CEDAR / DSW type solution

   1. Most researchers will probably want to have a solution that takes little effort, but does meet the requirements imposed by employers, funders, etc.

   2. Health-RI provides easy to use forms with mandatory and optional fields as required by (initially) the core metadata schema and (later) extended metadata schemas

      1. Forms must have guidance to help researchers properly fill in the necessary data. Guidance could e.g. be (sections of) metroline pages

   3. Output should be something suitable for a FAIR Datapoint or Catalog (harvestable by Health-RI)

      1. Maybe even nicer if you could provide it to an FDP directly as an export option?

         1. E.g. You’re an Amsterdam UMC researcher it could suggest a specific FDP

2. Advanced Track - A manual solution [Dena: Advance track cannot be fully manual]] So I am wondering as we previously discussed we need to have a scenario where we define semi-automatic approach for extracting data, mapping and transformation and api creation]]

   1. The Basic Track does not meet your demands or you just prefer to do it manually

   2. Health-RI provides guidance (recipes, perhaps scripts/software if it makes sense)

      1. The process should be able to start with nothing and end with having reached your goals

      2. Core can probably have a follow-along example; for extended maybe pick one for follow-along example

      3. Custom stuff should have clear guidance where possible with also recipes for domain specific problems.

         1. If custom things can be generalised to apply to e.g. more domains, that would be better

         2. Also, it may be useful to keep track of custom items? If lots of projects add the same custom item, it could be useful to add it to a new version of core.

Scenarios

Basic Track

• BT1 - Make Simple Dataset Discoverable & Searchable using DSW - Core

• BT2 - Make Simple Dataset Discoverable & Searchable using DSW - Core + Extension

• BT3 - Make Simple Dataset Discoverable & Searchable using DSW - Core (+ Extension) + Custom

  • Unfeasible: custom does not seem realistic in a DSW approach as HRI would need to create new forms for every project with custom items

Advanced Track

• AT1 - Make Simple Dataset Discoverable & Searchable using Manual approach - Core

• AT2 - Make Simple Dataset Discoverable & Searchable using Manual approach - Core + Extension

• AT3 - Make Simple Dataset Discoverable & Searchable using Manual approach - Core (+ Extension) + Custom

...