Configurable servers

[igoroctaviano]

Currently, the viewer passes dicomweb configuration from the environment variables directly to the app component.

We should create a public viewer configuration that would have server configuration in it that the correct server layer would consume.

The viewer could provide a mechanism to add different DICOM data sources through the same common interface. This way the viewer will interact with metadata in an indirect way.

[fedorov]

Suggestion from @pieper:

I would suggest that the GCP case is common enough that you might want to include a handler for it. You could have a url like:

https://slite.org/slim/gcp/dataset/dicomstore/

Then you could have other cases where gcp is replaced by aws or mgbvna or whatever.

[fedorov]

This is done, effectively, since there is already an option to add a DICOMweb endpoint in the appllication UI.

Let's add information how this feature can be enabled in the app config, and a screenshot how it looks in the UI, and close.

[fedorov]

Let's use wiki for documentation for now, can revisit later. https://github.com/ImagingDataCommons/slim/wiki

[fedorov]

For the reference, there are different features related to configurable servers:

• specify main server through the UI - this is available via the link icon
• specify secondary server that is designed to support the use case where annotations are fetched from a server different from the main server for a study that exists in both servers - this is available
• specify main server in the URL - as it is possible in OHIF - this is not available

[fedorov]

Let's trim spaces from the URL inserted into the external server UI! But once that is done, feel free to close it @igoroctaviano !

[fedorov]

This issue should be resolved once the WG26 connectathon is over and the branch that is used there is merged.

[igoroctaviano]

@pedrokohler to implement trim space for the server selector component.