OHDSI / OHDSI/FeatureExtraction
Use semicolon instead of comma as separator in table 1 specifications
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 74
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Currently table 1 specifications require comma-separated values within columns (see for example here ). It makes more sense to use semicolons instead.
(Make sure to be backwards compatible)
Contributor guide
No contributing guide indexed for this repository
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 with inst/csv/Table1Specs.csv and trace how table 1 specifications are parsed in the R package. Done means semicolon-separated values work while existing comma-separated specifications remain supported. Check the project's existing tests or parsing coverage for both formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100