Difference between revisions of "Slicer4:Remote Data Handling"
m (Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2") |
|||
Line 7: | Line 7: | ||
=== Slicer3 === | === Slicer3 === | ||
− | Slicer3 had [[Slicer3:Remote_Data_Handling|remote data functionality]] integrated with the core MRML code and exposed via several user oriented interfaces including [ | + | Slicer3 had [[Slicer3:Remote_Data_Handling|remote data functionality]] integrated with the core MRML code and exposed via several user oriented interfaces including [[Modules:MainApplicationGUI-Documentation-3.6#View_menu|a download dialog]] and [[Modules:FetchMI-Documentation-3.6|the FetchMI module]]. |
=== DICOM === | === DICOM === | ||
Line 13: | Line 13: | ||
In slicer4, we also wish to expose query/retrieve functionality based on DICOM protocols, as implemented [http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011#End_User_Functionality in CTK]. | In slicer4, we also wish to expose query/retrieve functionality based on DICOM protocols, as implemented [http://www.commontk.org/index.php/CTK-Hackfest-Feb-2011#End_User_Functionality in CTK]. | ||
− | Midas also provides data server functionality, with [ | + | Midas also provides data server functionality, with [[File:MIDASDesktop.png|unique interface possibilities]]. |
== Open Questions == | == Open Questions == |
Latest revision as of 02:31, 27 November 2019
Home < Slicer4:Remote Data HandlingOverview
This page is for discussion of read/write access to data server and how Slicer3's remote data functionality should evolve in Slicer4.
Discussion of this topic is part of the NA-MIC 2011 Summer Project Week.
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 .
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?