-
Couldn't load subscription status.
- Fork 7
Exploring at the network-level: Related Interactions #988
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
Conversation
…ated text between PMIDS
- comment out interaction/doc ranking logic
- simply do not back-fill interactions with document related papers
… (selection) - Create reusable loading and paper components - first pass at the related interaction list element display
- Make hypertext colored blue
- Improve the readability of the excerpts display
… collection, if exists - Show the data source in the interaction-level display
- add some extra fields from INDRA to the interaction/source
- link styling and naming
|
@jvwong, would you merge this in and link to a live example of the results on the unstable instance? The code looks OK, and I'd like to have a live example to point to in order to comment on the UI. |
|
OKey, I'll put in on master.factoid.baderlab.org - ping you when its done |
|
@maxkfranz I updated the site, and kicked off an example: https://master.factoid.baderlab.org/document/e5dc3eef-6af0-4c61-8a42-ddeb4a4285b5 |
|
Looks good. Minor feedback:
|
|
We've try to mitigate failures and provide fall-backs upon
Another existing issue is that when semantic-search returns an error, for whatever reason (PathwayCommons/semantic-search#98) there is no reasonable fallback herein, which ultimately leads to no related papers - its 'all or none'. All of these points of failure should be considered in this PR since the relevant code is being updated. |
# Conflicts: # src/config.js
# Conflicts: # src/server/routes/api/document/index.js
…STATEMENTS_ELEMENT for each entity.
This is a prototype. Displays more detail of INDRA search results upon interacting with elements of the network in our Explorer.
The original motivation for this feature was to provide more explicit information about why the papers were being displayed for a given network element.
element.relatedPapersdata with the existing schema, or if in fact none were foundRefs #937