Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
MEDS-DEV Results should track dataset metadata (e.g., versions)
Open
Nobody has claimed this yet.
enhancement
good first issue
priority:high
Results storage and tracking
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
This is implicit (to a point) in the MEDS-DEV version, but we should track it explicitly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify any files, tests, or entry points. First clarify which MEDS-DEV results should carry dataset metadata, which metadata fields are required, and how versions should be represented. Done should include explicit dataset metadata in results with reproducibility requirements and corresponding validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100