Preserve the origin story of package data
Open
Nobody has claimed this yet.
documentation
- Dominant language
- R
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Would be useful to clearly document how the datasets under data/ were generated (with code).
For example, metalite and metalite.ae both have scripts under data-raw/, suggested by the R Packages book.
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
Review the datasets under data/ and the corresponding generation scripts under data-raw/, starting with metalite and metalite.ae. Follow the R Packages book's data/data-raw guidance and document how the datasets were generated, including links to the code. Done when the dataset origin stories and generation process are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100