Slicer4:Remote Data Handling
Overview
This page is for discussion of read/write access to data server and how Slicer3's remote data functionality should evolve in Slicer4.
Background
Slicer3
Slicer3 had remote data functionality integrated with the core MRML code and exposed via several user oriented interfaces including a download dialog and the FetchMI module.
DICOM
In slicer4, we also wish to expose query/retrieve functionality based on DICOM protocols, as implemented in CTK.
Midas also provides data server functionality, with unique interface possibilities.
Open Questions
What are the user community priorities for supporting remote data resources?
Is working within the DICOM standard a priority, or would a more generic web services structure (REST api) better support user needs?
How much time and effort should be dedicated to remote IO compared to other slicer4 projects?