I had dumped some ideas for a few immediate use cases in case of DANDI at https://github.com/dandi/dandiarchive/wiki/WiP:-dump-of-thoughts-on-%22services-registry%22 .
For some it might be necessary to adjust CORR settings of the web server hosting our web ui. I think registry should include that information and then any particular website deployment should have somewhere (top level .git/config?) settings to which services to enable. But with that enabled we already have support for redirecting for any file we host to bioimagesuiteweb (visit example).
So if we establish such registry, then any e.g. .nii.gz file could have a context menu pop up with "Single View on bisweb".
If web interface could support selection of multiple files, or adding them into some kind of a "queue", we could add action for multiple like "Overlay View on bisweb", etc.
I had dumped some ideas for a few immediate use cases in case of DANDI at https://github.com/dandi/dandiarchive/wiki/WiP:-dump-of-thoughts-on-%22services-registry%22 .
For some it might be necessary to adjust CORR settings of the web server hosting our web ui. I think registry should include that information and then any particular website deployment should have somewhere (top level .git/config?) settings to which services to enable. But with that enabled we already have support for redirecting for any file we host to bioimagesuiteweb (visit example).
So if we establish such registry, then any e.g. .nii.gz file could have a context menu pop up with "Single View on bisweb".
If web interface could support selection of multiple files, or adding them into some kind of a "queue", we could add action for multiple like "Overlay View on bisweb", etc.