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
Allow BFF to determine multiscene collection to load in VolE.
Solution
Get some example data from Antoine.
Use BFF to export CSV.
Load CSV into app, each row is one scene. Use File Path column as zarr source and all other columns as metadata entries per scene.
For prototyping, this could be drag n drop or a new (maybe temporary) url parameter.
The text was updated successfully, but these errors were encountered:
Implementation strategy:
At csv export time, BFF can create an iframe and load a stub page from the VolE domain (vole.allencell.org or whatever).
Then we can postmessage from bff into the iframe, with the contents of the csv data.
Then the vole stub page can use local storage to save the data.
Then BFF can launch VolE in a new tab, and hand it an id that lets it load the same data from local storage, and clean it up if needed.
The reason for the iframe is that localstorage reads and writes have to have same origin...
Use Case
Allow BFF to determine multiscene collection to load in VolE.
Solution
Get some example data from Antoine.
Use BFF to export CSV.
Load CSV into app, each row is one scene. Use File Path column as zarr source and all other columns as metadata entries per scene.
For prototyping, this could be drag n drop or a new (maybe temporary) url parameter.
The text was updated successfully, but these errors were encountered: