elixir-europe / elixir-europe/human-data-maturity-model

Adjust levels of technical areas to allow for tested with synthetic data

Open
#12 0 comments 0 reactions 0 assignees View on GitHub
Levels
Dominant language
HTML
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

From pilot kick off:
Dylan: since this is functionality based, I’m not sure whether you need to know if the data is available, then it should be a separate part of the process. A way of doing this could be to say “the functionality has been demonstrated with synthetic data” and then real data. Align with GDI TRLs

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by reviewing the proposed separation between synthetic and real data and the GDI TRLs; clarify how technical-area levels should change and what “demonstrated with synthetic data” means. Done means the levels and process explicitly distinguish synthetic-data testing from real-data validation.

Written by the indexing model from the issue text.

Assessment

Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.