Difference between revisions of "Talk:2012 Summer Project Week:XNATSlicerIntegration"
(Created page with ' 1) Download and view scans (as DICOMS). 2) Create and upload Slicer Scenes to XNAT, using XNAT-downloaded scans OR locally stored files. 3) Any uploaded Slicer scene package …') |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | == Detailed Objectives == | ||
| − | + | 1) Download and view scans (as DICOMS).<br> | |
| − | 1) Download and view scans (as DICOMS). | + | 2) Create and upload Slicer Scenes to XNAT, using XNAT-downloaded scans OR locally stored files.<br> |
| − | 2) Create and upload Slicer Scenes to XNAT, using XNAT-downloaded scans OR locally stored files. | + | 3) Any uploaded Slicer scene package that references XNAT data will be linked to the data via a URL. The module will recognize the remote links and conduct the necessary legwork such that when a scene is downloaded, the referenced files will also be downloaded. This involves parsing the mrmls, linking the referenced directories to XNAT URLs, for uploading scenes and vice-versa for downloading scenes.<br> |
| − | 3) Any uploaded Slicer scene package that references XNAT data will be linked to the data via a URL. The module will recognize the remote links and conduct the necessary legwork such that when a scene is downloaded, the referenced files will also be downloaded. This involves parsing the mrmls, linking the referenced directories to XNAT URLs, for uploading scenes and vice-versa for downloading scenes. | + | 4) Update Slicer scenes stored in XNAT. The interface will be contained entirely within Slicer. The end-state aims to leverage XNAT's web interface. The current state uses the XNAT REST API to construct a tree view.<br> |
| − | 4) Update Slicer scenes stored in XNAT. The interface will be contained entirely within Slicer. The end-state aims to leverage XNAT's web interface. The current state uses the XNAT REST API to construct a tree view. | + | 5) The widget will also allow for the storage and reference of Slicer-related files such as annotations, fiducials, volumes, etc. In the end-state, the widget will have the capacity to specifically isolate annotation files to be integrated in XNAT search queries.<br> |
| − | 5) The widget will also allow for the storage and reference of Slicer-related files such as annotations, fiducials, volumes, etc. In the end-state, the widget will have the capacity to specifically isolate annotation files to be integrated in XNAT search queries. | ||
Latest revision as of 15:38, 11 June 2012
Home < Talk:2012 Summer Project Week:XNATSlicerIntegrationDetailed Objectives
1) Download and view scans (as DICOMS).
2) Create and upload Slicer Scenes to XNAT, using XNAT-downloaded scans OR locally stored files.
3) Any uploaded Slicer scene package that references XNAT data will be linked to the data via a URL. The module will recognize the remote links and conduct the necessary legwork such that when a scene is downloaded, the referenced files will also be downloaded. This involves parsing the mrmls, linking the referenced directories to XNAT URLs, for uploading scenes and vice-versa for downloading scenes.
4) Update Slicer scenes stored in XNAT. The interface will be contained entirely within Slicer. The end-state aims to leverage XNAT's web interface. The current state uses the XNAT REST API to construct a tree view.
5) The widget will also allow for the storage and reference of Slicer-related files such as annotations, fiducials, volumes, etc. In the end-state, the widget will have the capacity to specifically isolate annotation files to be integrated in XNAT search queries.
