Slicer4:Remote Data Handling - Revision history

Grundlett: Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

2019-11-27T02:31:56Z

Text replacement - "\[http:\/\/www\.slicer\.org\/slicerWiki\/index\.php\/([^ ]+) ([^]]+)]" to "$2"

Pieper: /* Overview */

2011-05-25T15:56:34Z

Overview

Pieper: Created page with '==Overview== This page is for discussion of read/write access to data server and how Slicer3's remote data functionality should evolve in Slicer4…'

2011-05-25T15:55:19Z

Created page with '==Overview== This page is for discussion of read/write access to data server and how Slicer3's remote data functionality should evolve in Slicer4…'

New page

==Overview==
This page is for discussion of read/write access to data server and how [[Slicer3:Remote_Data_Handling|Slicer3's remote data functionality]] should evolve in Slicer4.

==Background==

=== Slicer3 ===
Slicer3 had [[Slicer3:Remote_Data_Handling|remote data functionality]] integrated with the core MRML code and exposed via several user oriented interfaces including [http://www.slicer.org/slicerWiki/index.php/Modules:MainApplicationGUI-Documentation-3.6#View_menu a download dialog] and [http://www.slicer.org/slicerWiki/index.php/Modules:FetchMI-Documentation-3.6 the FetchMI module].

=== DICOM ===

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 [http://www.slicer.org/slicerWiki/index.php/File:MIDASDesktop.png 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?

@@ Line 7: / Line 7: @@
 === Slicer3 ===
-Slicer3 had [[Slicer3:Remote_Data_Handling|remote data functionality]] integrated with the core MRML code and exposed via  several user oriented interfaces including [http://www.slicer.org/slicerWiki/index.php/Modules:MainApplicationGUI-Documentation-3.6#View_menu a download dialog] and [http://www.slicer.org/slicerWiki/index.php/Modules:FetchMI-Documentation-3.6 the FetchMI module].
+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 ===
@@ 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].
-Midas also provides data server functionality, with [http://www.slicer.org/slicerWiki/index.php/File:MIDASDesktop.png unique interface possibilities].
+Midas also provides data server functionality, with [[File:MIDASDesktop.png|unique interface possibilities]].
 == Open Questions ==

@@ Line 1: / Line 1: @@
 ==Overview==
 This page is for discussion of read/write access to data server and how [[Slicer3:Remote_Data_Handling|Slicer3's remote data functionality]] should evolve in Slicer4.
 ==Background==