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
It would be cool if fusion-builder allowed us to populate a fusion based on submitted nomenclature strings (GET) or JSON objects (POST).
Use case
If you want to visualize what a fusion is based on the fusion nomenclature description, you could link to the fusion builder with that string and automatically populate the build elements accordingly, allowing people to explore it.
Proposed solution
A user creates a link for an assayed fusion like https://fusion-builder.cancervariants.org/lookup?q="v::ALK" and this is resolved into a categorical fusion object with multi-partner gene and ALK gene elements.
For POST queries of full JSON objects, a fusion may include properties outside just the nomenclature. These queries would provide URL links that redirect to a saved fusion build, e.g. https://fusionbuilder.cancervariants.org/lookup/aEbej4X, that is retrievable for viewing by web browser. Similarly, after manually building a fusion, a user could "save" that fusion for sharing by creating such a link directly from the UI and sharing it.
Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
None
The text was updated successfully, but these errors were encountered:
Feature description
It would be cool if fusion-builder allowed us to populate a fusion based on submitted nomenclature strings (GET) or JSON objects (POST).
Use case
If you want to visualize what a fusion is based on the fusion nomenclature description, you could link to the fusion builder with that string and automatically populate the build elements accordingly, allowing people to explore it.
Proposed solution
A user creates a link for an assayed fusion like
https://fusion-builder.cancervariants.org/lookup?q="v::ALK"
and this is resolved into a categorical fusion object with multi-partner gene and ALK gene elements.For POST queries of full JSON objects, a fusion may include properties outside just the nomenclature. These queries would provide URL links that redirect to a saved fusion build, e.g.
https://fusionbuilder.cancervariants.org/lookup/aEbej4X
, that is retrievable for viewing by web browser. Similarly, after manually building a fusion, a user could "save" that fusion for sharing by creating such a link directly from the UI and sharing it.Alternatives considered
No response
Implementation details
No response
Potential Impact
No response
Additional context
No response
Contribution
None
The text was updated successfully, but these errors were encountered: