obophenotype / obophenotype/chiro
Consider relabeling CHEBI roles
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
or assigning 'obo foundry unique label'. E.g. 'antineoplastic agent' is named and defined as if it were the substance rather than the role. If we are serious about the role hierarchy being a role hierarchy then things should be named and defined like roles.
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
No files, tests, or entry points are identified. Start by reviewing the CHEBI role hierarchy and the “antineoplastic agent” example; the work is done when affected roles are consistently named and defined as roles, or assigned an OBO Foundry unique label.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100