Match highlighted orthologue by gene and species #1091
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In conjunction with eg-web-common PR 143 and eg-web-metazoa PR 46, this PR would:
s1
parameter with the gene-tree links in an orthologue table, whose value is the URL of the species containing the given orthologue;s1
parameter to gene-tree views, which is expected to contain the species URL of the genome containing the gene specified byg1
;s1
to help unambiguously identify the gene specified byg1
for highlighting in a given gene-tree view; and'_leaves'
item of node features in thegenetree
GlyphSet to identify leaves by their concatenatedgenome_db_id
and gene stable ID, making it possible for a highlighted orthologue to be identified even if in a collapsed branch of the gene tree.Views affected
This is expected to affect gene-tree views in which an orthologue is highlighted, such as those linked from the
ComparaOrthologs
view.Some example links have been added to the related JIRA issue.
Possible complications
Complications are not expected, as the
s1
parameter has not (as far as I know) been used in aComparaTree
component, and the'_leaves'
item of node features should be safe to repurpose as they are not (as far as I know) currently used.Merge conflicts
None detected.
Related JIRA Issues (EBI developers only)