Difference between revisions of "CTSC Slicer XNE"

From NAMIC Wiki
Jump to: navigation, search
Line 7: Line 7:
 
* Authentication dialog presented
 
* Authentication dialog presented
 
* Dialog input is processed
 
* Dialog input is processed
* XNAT queried for projects & GUI populated
+
* XNAT queried for projects  
 +
* response is checked for http error codes
 +
* xml parsed to get list of projects
 +
* GUI populated
 
* One project selected
 
* One project selected
* XNAT queried for subjects in that project & GUI populated
+
* XNAT queried for subjects in that project
 +
* response is checked for http error codes
 +
* xml parsed to get list of subjects
 +
* GUI populated
 
* One subject selected
 
* One subject selected
 
* User selects filters to narrow scan search
 
* User selects filters to narrow scan search
* User selects "search" for all scans & GUI populated
+
* User selects "search" for all scans  
 +
* XNAT queried for appropriate scans
 +
* response is checked for http error codes
 +
* xml is parsed to get list of scans
 +
* GUI is populated
 
* User selects one scan and "download"
 
* User selects one scan and "download"
 
* Scan is loaded into Slicer
 
* Scan is loaded into Slicer
Line 29: Line 39:
 
  curl -d POST $XNE_Host/REST/JSESSION -u $XNE_UserName:$XNE_Password
 
  curl -d POST $XNE_Host/REST/JSESSION -u $XNE_UserName:$XNE_Password
  
=== 4. Query XNAT for Projects Available to User; Populate GUI ===
+
=== 4. Query XNAT for Projects Available to User ===
 +
 
 +
* XNAT queried for appropriate projects
 +
* response is checked for http error codes
 +
** if error is found, report to user
 +
** else xml is parsed to get list of scans
  
 
=== 5. User Selects One Project ===
 
=== 5. User Selects One Project ===
  
=== 6. Query XNAT for Subjects in Selected Project; Populate GUI ===
+
=== 6. Query XNAT for Subjects in Selected Project ===
 +
 
 +
* XNAT queried for appropriate subjects
 +
* response is checked for http error codes
 +
** if error is found, report to user
 +
** else xml is parsed to get list of scans
  
 
=== 7. User Selects One Subject ===
 
=== 7. User Selects One Subject ===
Line 39: Line 59:
 
=== 8. User Selects Pull-Down Filters to Narrow Search for Scans & Selects Search ===
 
=== 8. User Selects Pull-Down Filters to Narrow Search for Scans & Selects Search ===
  
=== 8. Query XNAT for All Scans for This User; Populate GUI ===
+
=== 8. Query XNAT for All Scans for This User ===
 +
 
 +
* XNAT queried for appropriate scans
 +
* response is checked for http error codes
 +
** if error is found, report to user
 +
** else xml is parsed to get list of scans
  
 
=== 10. User Selects One Scan and Clicks Download ===
 
=== 10. User Selects One Scan and Clicks Download ===
  
 
=== 11. Scan is Loaded into Slicer ===
 
=== 11. Scan is Loaded into Slicer ===

Revision as of 15:56, 4 August 2009

Home < CTSC Slicer XNE

UXP & functionality planning for Slicer's XNE client

Workflow & Implementation approaches

All Workflow Steps:

  • Log in to XNAT Enterprise instance
  • Authentication dialog presented
  • Dialog input is processed
  • XNAT queried for projects
  • response is checked for http error codes
  • xml parsed to get list of projects
  • GUI populated
  • One project selected
  • XNAT queried for subjects in that project
  • response is checked for http error codes
  • xml parsed to get list of subjects
  • GUI populated
  • One subject selected
  • User selects filters to narrow scan search
  • User selects "search" for all scans
  • XNAT queried for appropriate scans
  • response is checked for http error codes
  • xml is parsed to get list of scans
  • GUI is populated
  • User selects one scan and "download"
  • Scan is loaded into Slicer

Each step is detailed below.

1. Log in to Enterprise

2. Authentication Dialog Presented

3. Process Dialog Input

  • Save the username (XNE_UserName) and password (XNE_Password)
  • Authenticate and create a session:
curl -d POST $XNE_Host/REST/JSESSION -u $XNE_UserName:$XNE_Password

4. Query XNAT for Projects Available to User

  • XNAT queried for appropriate projects
  • response is checked for http error codes
    • if error is found, report to user
    • else xml is parsed to get list of scans

5. User Selects One Project

6. Query XNAT for Subjects in Selected Project

  • XNAT queried for appropriate subjects
  • response is checked for http error codes
    • if error is found, report to user
    • else xml is parsed to get list of scans

7. User Selects One Subject

8. User Selects Pull-Down Filters to Narrow Search for Scans & Selects Search

8. Query XNAT for All Scans for This User

  • XNAT queried for appropriate scans
  • response is checked for http error codes
    • if error is found, report to user
    • else xml is parsed to get list of scans

10. User Selects One Scan and Clicks Download

11. Scan is Loaded into Slicer