To be redirected to a child term's record when I open it in another tab.
To have all child terms of the current one already displayed by default.
1. Opening terms in other tabs
When I navigate through the tree view of an ontology I usually like to open several tabs with different ontology terms of such hierarchy. So, instead of clicking on each child term, having to constantly change records, I prefer to have several open at once to compare them. This is severely hindered by the behaviour that I have observed with the tree view:
Left clicking a term (e.g. Fluidigm C1 microfluidics platform - EFO:0009990) redirects you to its correct record:
Copying the term's URL (e.g. right-click + copy link address) or using the command to open it in another tab automatically (e.g. central click) redirects you to the current record you are in (e.g. instrument - EFO:0000548):
So, for example, if we start at the instrument (https://www.ebi.ac.uk/ols/ontologies/efo/terms?short_form=EFO_0000548) record, I would click on the + sign to display its child terms, among which I would find Fluidigm C1 microfluidics platform (EFO:0009990). If I want to open its content, the only way I can is to directly left click on it, losing my current status of the tree view. Instead, I would prefer to open this new term (EFO:0009990) in a new tab without losing the current tree view.
2. Child terms of the current term displayed by default
Similar to what the Show all siblings feature does (...siblings=true), I would very much like a feature displaying the child terms one level below of the current term by default in the tree view. This would save me the above mentioned step of having to always click on + when going down a hierarchy. I believe that would be easier to navigate, given that the parental hierarchy would still be straightforward without their siblings, but I would easily go down the conceptual hierarchy level by level.
For instance, if I we start at array term (http://www.ebi.ac.uk/efo/EFO_0002698), I would like to, by default, have its three children displayed in the tree view: DNA array, array reporter and protein array. Going from the first image to the second image:
Summary
1. Opening terms in other tabs
When I navigate through the tree view of an ontology I usually like to open several tabs with different ontology terms of such hierarchy. So, instead of clicking on each child term, having to constantly change records, I prefer to have several open at once to compare them. This is severely hindered by the behaviour that I have observed with the tree view:
Fluidigm C1 microfluidics platform
-EFO:0009990
) redirects you to its correct record:instrument
-EFO:0000548
):So, for example, if we start at the
instrument
(https://www.ebi.ac.uk/ols/ontologies/efo/terms?short_form=EFO_0000548) record, I would click on the+
sign to display its child terms, among which I would findFluidigm C1 microfluidics platform
(EFO:0009990
). If I want to open its content, the only way I can is to directly left click on it, losing my current status of the tree view. Instead, I would prefer to open this new term (EFO:0009990
) in a new tab without losing the current tree view.2. Child terms of the current term displayed by default
Similar to what the Show all siblings feature does (
...siblings=true
), I would very much like a feature displaying the child terms one level below of the current term by default in the tree view. This would save me the above mentioned step of having to always click on+
when going down a hierarchy. I believe that would be easier to navigate, given that the parental hierarchy would still be straightforward without their siblings, but I would easily go down the conceptual hierarchy level by level.For instance, if I we start at
![Second image](https://user-images.githubusercontent.com/77288380/154494215-abed57a3-b0f4-43a6-823b-244a95c5cd7b.png)
array
term (http://www.ebi.ac.uk/efo/EFO_0002698), I would like to, by default, have its three children displayed in the tree view:DNA array
,array reporter
andprotein array
. Going from the first image to the second image: