Imageomics / Imageomics/TaxonoPy
Resolved common names should not allow variable input data through
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In def merge_common_name of src/taxonopy/resolve_common_names.py, input data for common names should not be given deference when it is present. This may lead to vernacular variability for a given resolved hierarchy.
The common name should always be derived from the backbone lookup files for uniform one-to-one mapping between taxonomy and vernacular.
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 in src/taxonopy/resolve_common_names.py at def merge_common_name and inspect how the backbone lookup files and input common-name data are currently combined. Done means the common name for a resolved hierarchy is consistently derived from the backbone lookup files rather than variable input data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100