INCATools / INCATools/ontology-access-kit
Decide on default colors for each ontology in OAK configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 198
- Forks
- 35
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 1
Description
We have some default colors for some ontologies in our kgviz stylesheet:
Anyone can provide their own stylesheet, but it's useful to have a default base that serves a broad range of scenarios
I am not sure if there is any good criteria for deciding. A general principle is that frequently "adjacent" ontologies (whether by is-a, e.g. upper ontologies to subsumed ontologies) should be in easily distinguishable colors, as should "analogous" ontologies (e.g a common use case is looking at MP and HP side by side).
If there is no appetite for this then we can close this issue and just let the default stylesheet evolve naturally
See also:
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
Review src/oaklib/conf/obograph-style.json, especially lines 84-130, to understand the existing ontology colors and stylesheet structure. Use the adjacency and analogous-ontology examples in the issue as starting criteria, and consult obo-relations issue 613. Done means an agreed default color scheme is recorded in the stylesheet, or the issue is closed if there is no appetite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100