You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2019. It is now read-only.
This starts getting in to heavier UI development, so we should discuss the game plan before committing to implementing this ticket. But, imagine the scenario below:
currently I can add all 14 of those WP pathways to the network, but they show up as separate nodes. Suppose I want to get all genes associated with any of those pathways. I would want to aggregate them into a single node. If I click that node, it should show me services that take that node type. If I click a service, then the explorer should execute 14 calls for each of those pathways (or even better, a single query that combines those 14 pathways).
The text was updated successfully, but these errors were encountered:
This starts getting in to heavier UI development, so we should discuss the game plan before committing to implementing this ticket. But, imagine the scenario below:
![2017-05-25_16-07-05](https://cloud.githubusercontent.com/assets/2635409/26474241/c2ec911c-4164-11e7-801d-3be77c8d5cb0.png)
currently I can add all 14 of those WP pathways to the network, but they show up as separate nodes. Suppose I want to get all genes associated with any of those pathways. I would want to aggregate them into a single node. If I click that node, it should show me services that take that node type. If I click a service, then the explorer should execute 14 calls for each of those pathways (or even better, a single query that combines those 14 pathways).
The text was updated successfully, but these errors were encountered: