Medical-Event-Data-Standard/MEDS-DEV

MEDS-DEV Results should track dataset metadata (e.g., versions)

Open

#206 opened on Mar 26, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (9 forks)github user discovery
Results storage and trackingenhancementgood first issuepriority:high

Repository metrics

Stars
 (39 stars)
PR merge metrics
 (Avg merge 21d 12h) (6 merged PRs in 30d)

Description

This is implicit (to a point) in the MEDS-DEV version, but we should track it explicitly.

Contributor guide

Research direction
Investigate the current MEDS DEV result structures to identify where dataset metadata (e.g., versions) is implicitly tracked, then design and implement explicit metadata fields to be stored alongside results.
Tech stack
python
Domain
datamachine learning
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70