...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Note:
UMCs may well provide their own local tools/software and may not need HRI for basic onboarding in the HRI Catalogue.
If HRI does want to offer a tool for filling in the Metadata schema (core/petals):
CEDAR will not be used (discussed 24-10-2023, Marianne)
Data Stewardship Wizard (DSW) could maybe be used (Suggestion Rob Hooft).
Keep in mind that if the scenarios mention the DSW this could be another tool. No choice has been made.
...
Proposal: have two main solutions. To stick with the Metroline Analogy: a Basic and an Advanced Track:
Basic Track - A fillable form-based solution, such as CEDAR or the DSW
Most researchers will probably want to have a solution that takes little effort, but does meet the requirements imposed by employers, funders, etc.
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
Forms must have guidance to help researchers properly fill in the necessary data. Guidance could e.g. be (sections of) metroline pages
Output should be something suitable for a FAIR Datapoint or Catalog (harvestable by Health-RI)
Maybe provide the output directly to an FDP as an export option?
E.g. You’re an Amsterdam UMC researcher it could suggest an Amsterdam UMC preferred FDP
It would need some form of quality control / permission before the “ok, send it” button could be pressed?
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]]
The Basic Track does not meet your demands or you just prefer to do it manually
Health-RI provides guidance (knowledge, references, recipes, perhaps scripts/software where possible)
Core can probably have a follow-along example; for extended maybe pick one extension for a follow-along example
Metadata elements outside of the core and extensions should have clear guidance where possible with also recipes for domain specific problems.
If custom things can be generalised to apply to e.g. more domains, that would be better
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.
Scenario List
Basic Track
BT1 - Make Simple Dataset Findable using Datastewardship Wizard - Core
BT2 - Make Simple Dataset Findable using Datastewardship Wizard - Core + Extension
BT3 - Make Simple Dataset Findable using Datastewardship Wizard - Core (+ Extension) + Custom
Probably 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 Findable using Semi-automatic approach - Core
AT2 - Make Simple Dataset Findable using Semi-automatic approach - Core + Extension
AT3 - Make Simple Dataset Findable using Semi-automatic approach - Core (+ Extension) + Custom
...