Medical-Event-Data-Standard / Medical-Event-Data-Standard/MEDS-DEV
We need to export a code-endpoint releasing the information about supported tasks in a friendly format.
Open
Nobody has claimed this yet.
- #211 by @mmcdermott — closed without merging
Blocking External Use
priority:critical
Tasks
Testing
Usability/Interface
Website / Branding
- Dominant language
- Python
- Stars
- 43
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Blocking:
- #151
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
Start by reviewing the closed pull request #211 and locating the repository's existing code-endpoint or task-export entry point. Compare the current implementation with the four requested outputs: names, README files, metadata blocks, and refs.bib files. Done means all four are captured and exported through a friendly endpoint format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100