Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
We need to export a code-endpoint releasing the information about supported models in a friendly format.
Open
Nobody has claimed this yet.
- #211 by @mmcdermott — closed without merging
Blocking External Use
Models
priority:critical
Testing
Usability/Interface
Website / Branding
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Blocking:
- #152
This entails capturing and exporting:
- Names
- README files
- Metadata blocks
-
refs.bibfiles
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
No files or tests are named. Start by locating the code endpoint and the supported-model definitions, then trace how Names, README files, metadata blocks, and refs.bib files are represented. Done means the endpoint exports all four categories in a friendly format and relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100