Create "data GH repos"
- Dominant language
- R
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We have identified a few data objects that need version control, a version release system and an automated QC flow.
For these objects, we will create new "data repositories" on GH -- being mindful that the individual size of each dataset _must_ be small (under 50MB).
[data object -> repo]
- [ ] BECdb -> **bcgov/SS_ssBC_data** (⭐ in https://github.com/bcgov/CCISS/issues/50)
- [ ] US site series -> **bcgov/SS_ssUS_data** (🔵 in https://github.com/bcgov/CCISS/issues/50)
- [ ] AB site series -> **bcgov/SS_ssAB_data** (➕ in https://github.com/bcgov/CCISS/issues/50)
- [ ] site series table -> **bcgov/SS_feasTables_data** (🔺in https://github.com/bcgov/CCISS/issues/50)
- [ ] edatopic table -> **bcgov/SS_feasTables_data** (🔺in https://github.com/bcgov/CCISS/issues/50)
- [ ] feasibility table -> **bcgov/SS_feasTables_data** (🔺in https://github.com/bcgov/CCISS/issues/50)
- [ ] CF reference guide -> **bcgov/SS_CFRG_data** (💙 in https://github.com/bcgov/CCISS/issues/50)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing issue #50 and the repository mappings listed here. Check the proposed GitHub repositories and confirm how version control, releases, and automated QC should apply to each data object, including the under-50MB constraint. Done means the required data repositories and their agreed workflows are created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- data, devops, release, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100