obophenotype / obophenotype/ncbitaxon
Provide standard place for union taxa
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
carried from https://github.com/EnvironmentOntology/envo/issues/1046
GO mints union taxa in a fake namesapce, NCBITaxon_Union. See https://bmcbioinformatics.biomedcentral.com/articles/10.1186/1471-2105-11-530
PCO is making union taxa in the PCO namespace https://github.com/PopulationAndCommunityOntology/pco/issues/58
we should have a single place for union taxa. This should not be injectedinto the ncbitaxon namespace as ncbi don't make these. however, releases should be synced with ncbitaxon. we should use the go union pattern
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 linked ENVO and PCO issues, the cited GO union pattern, and the NCBITaxon release context. The issue names no files or tests; done requires a maintainer-approved shared namespace and clear expectations for synchronizing releases without placing union taxa in the NCBITaxon namespace.
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
- 25/100