galaxyproject / galaxyproject/idc
Repository and data structure
- Dominant language
- Shell
- Stars
- 10
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
- What repositories should we have? Suggestions so far include:
- Sequence data, non-sequence-data
- One per family (sequence data), one for periodically updated data (blast DBs, kraken, snpeff), one for everything else
- One per genome (CVMFS technical limitations?)
- What should the structure inside the repositories be? Suggestions so far include:
- NCBI taxon
- By indexer/DM
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with issue #9 and compare its proposed repository splits with the suggested structures inside repositories. No implementation files or tests are named; the work is complete only after the repository organization and internal layout have been agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100