Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interactions: Provide more informative label for edge tooltip links to "Detailed Views" #1099

Open
jvwong opened this issue Sep 27, 2018 · 3 comments

Comments

@jvwong
Copy link
Member

jvwong commented Sep 27, 2018

Background

Within Interactions, edge tooltips display one or more SIF MEDIATOR_IDS under 'Pathway Links'.

image

Following link for [1] in this case gives a interaction from CTD

image

We could certainly provide more useful clues to help a user decide. I personally find detail in these links far more informative.

Ideas

Good: A traverse on each to fetch a list of the participant display names:

				"expression of CDKN1A protein",
				"CDKN1A protein",
				"TP53 protein/HSPB1 protein complex"

Better:?

Best: Max's idea of 'small multiple' preview snapshots

@maxkfranz
Copy link
Member

We need to consider the expense of doing many fetches for these links. There can be dozens or even hundreds of them.

@jvwong jvwong closed this as completed Oct 29, 2018
@jvwong jvwong reopened this Feb 11, 2019
@jvwong jvwong self-assigned this Feb 11, 2019
@jvwong jvwong changed the title Displaying links to MEDIATOR_IDS: Ideas Interactions: Provide more informative label for edge tooltip links to "Detailed Views" Feb 11, 2019
@jvwong
Copy link
Member Author

jvwong commented Feb 11, 2019

We now slot this list of numbered links under the tooltip subheading "Open a more detailed view of this interaction". And indeed, the caveat is that these can be lengthy in a few cases:

interactions_tooltip_edge_tp53-mdm2

@jvwong
Copy link
Member Author

jvwong commented Feb 11, 2019

I propose to implement the approach described above, that is, traversal to fetch gene and interaction names. Indeed, we (1) already possess a rudimentary PC 'traverse' wrapper in src/server/external-services/pathway-commons.js and (2) traversals are rather lightweight in that multiple URIs for a given path can be done in a single GET.

Req'd tasks:

  • Modify traverse to accept multiple URIs for a given path
  • Create a function to map URI, path => genes/interaction text via traverse
  • Integrate into interactions data formatting getInteractionsCyJson

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants