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

Build a fusion from REST #329

Open
ahwagner opened this issue Sep 6, 2024 · 0 comments
Open

Build a fusion from REST #329

ahwagner opened this issue Sep 6, 2024 · 0 comments
Labels
enhancement New feature or request priority:low Low priority

Comments

@ahwagner
Copy link
Member

ahwagner commented Sep 6, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:low Low priority
Projects
None yet
Development

No branches or pull requests

1 participant