Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

The Quarantine feature should not be used for reviewing sessions for PII. Sessions that have been quarantined have already been permanently stored in the XNAT Archive. Even if a session is deleted from the Archive, a record of its metadata is still preserved in the project audit trail in the PostgreSQL database.

 


Autorun Pipelines

Pipeline processing can be set to run automatically when a session is moved into the XNAT archive. An example of this might be to run a protocol check to ensure that the session contains the number and type of scans that your project expects, or to run a quality check to look for common imaging artifacts. 

 


Archiving a Session

When an image session is archived, multiple things happen: 

...

As mentioned above, all of the information that is stored in the XNAT PostgreSQL database is permanently archived. This means that even if a session is marked for deletion, this merely updates the record in the database. Data is not actually destroyed or removed by any XNAT operation. 

 


Methods for Uploading Sessions

...

 


XNAT Upload Applet

Warning

Many browsers including Chrome and Safari have ended or will end support for embedded Java applications, signaling an upcoming end of life for the Java-based XNAT Upload Applet. We recommend using Firefox in the short term, or exploring other upload options listed below.

...

 


XNAT Desktop Upload Assistant

...

 


Compressed Image Uploader

...

 

 



Uploading via XNAT API

If you have large numbers of sessions to archive, you may consider writing a script to manage your uploads. Such a script would make use of the XNAT API to connect to your XNAT instance and perform the upload and archive functions. 


Uploading via DICOM Inbox

Another method of uploading large numbers of sessions involves moving your session files to a mounted file system that your XNAT server can access, then pointing the XNAT importer to it with a REST call. This bypasses the HTTP protocol during the import process, which can speed things up.