Both BRICS and FITBIR support the receipt of unprocessed brain images in DICOM format and processed images in a variety of formats including DICOM, MINC 1.0 and 2.0, Analyze, NIfTI-1, AFNI and SPM.
In order to ensure the quality of uploaded data and also to make data easy to query, the imaging data should be submitted in a specific format and range values should comply with the values defined in the data dictionary. All submitted research data must be validated against the values defined in the data dictionary prior to submission. To facilitate this process, we provide the Imaging Data Submission and Validation tool that assists researchers with the submission of imaging data. The tool is a component of the MIPAV (Medical Image Processing, Analysis, and Visualization) application. See also: BRICS data dictionary.
The Imaging Data Submission and Validation tool accepts the brain imaging data (in the form of brain image file and a CSV file) from a researcher and validates the metadata associated with the image files against the values defined in the data dictionary. It then creates an image submission package. The tool also provides a report of any data discrepancies, errors, and warnings received. If any validation errors are found, an image submission package cannot be created. In that case, the researched should edit data to fix all errors, first, and then re-validate the data.
See also:
The plug-in supports all file formats supported by MIPAV including processed and unprocessed brain images in DICOM format. If you are using different file format (not supported by MIPAV), please contact MIPAV support.
The most recent version of 64-bit Java Runtime Environment (JRE) (6 or 7) is required in order to run the Imaging Data Submission and Validation module.
Module input:
Module output:
Data can be uploaded in the form of a brain image file and a corresponding CSV file that contains some additional patient/subject/visit information (not stored in the image header) as well as image related metadata.
The following information is required for all image submissions:
The brain image file can be in the form of

Multifiles or multivolume image datasets (multivolumes) are image datasets, (e.g. DICOM datasets), composed of multiple files. These are 3D (3-dimensional) or 4D (4-dimensional, including time as a 4th dimension) image datasets that contain images of multiple slices. See also: Image formats descriptions and Opening image files in MIPAV.
Each image slice is a few millimeters thick and often can be considered as a 2D image. Each image of a single slice has a header that contains both:
A DICOM dataset can be stored on your computer as a set of multiple files - one file per each image slice. In that case it will occupy a whole directory.
To read more about DICOM image basics refer to "The Basic Structure of DICOM", by Charles Parisot, GE Medical Systems.
There are 2 ways on how you can include a DICOM image (or any other brain 3D or 4D image that has multiple slices) as multifile into the image submission package:
See also: Open as Multifile.
The structure of the CSV file should match a corresponding imaging form structure queryable by the query tool. See also: Using a CSV file.
For a sample CSV file please contact the Operations team - TBD.
If a researcher doesn't have a CSV file with metadata ready, he/she can use the Imaging Data Submission and Validation module to create one based on a chosen form structure.
See also: Using a form structure.
A form structure represents a grouping/collection of data elements used in BRICS data dictionary. A form structure is analogous to a case report form (CRF) (electronic or paper) where data elements are linked together for collection and display.
A data element is a logical unit of data used in BRICS. It contains a single piece of information of one kind. A data element has a name, precise definition, and a set of permissible values (codes), if applicable. A data element is not necessarily the smallest unit of data; it can be a unique combination of one or more smaller units. A data element occupies the space provided by field(s) on a paper/electronic case report form (CRF) or field(s) in a database record. BRICS allows a use of two types of data elements:
Both types of data elements are used in forms structures and to collect data.
The image submission package includes:




Before running the tool make sure that:
For a sample CSV file please contact the Operations team - TBD.
By default, the CSV file with metadata and the imaging file(s) should be located in the same directory.
When running the module you are asked to specify the Output directory which would be used by the module to store temporary files, validation logs, and image submission packages.
Specify the Output directory in the Output Directory for Validation tool box.
Recommendations:
Recommendations:

If you enter the image name into a CSV file in the "Image Information.ImgFileName" column, the Image Submission tool will read the information from the file header and populate it into the Edit Data Elements window.
For large data sets you can use a ZIP file, e.g. ImagingMR_1370626102276.zip file contains a DICOM dataset. See also: Multifiles and Opening an image as multifile.
If you need to manually upload image files,
If the image file did not appear in the directory you selected, check the files types listed in the Files of Type field located near the bottom of the dialog box.
To display all file types(recommended), select All Files or All.

Multifiles are image datasets (e.g. DICOM datasets) that are composed of multiple files. Each file contains a single image slice and has a header that contains both 1) the slice specific information and 2) the information about the whole dataset.
See also: Multifiles
To open an image as multifile:
The Preview Image box displays a thumbnail for the uploaded image.
In order to have a better preview, you can change Window and Level settings.
Use the Data Validation module to re-validate the CSV file from the image submission package. The Data Validation module assists researchers with the submission of both imaging and non-imaging data into the repository. The Data Validation module verifies that data conforms to the required format and range values defined in the data dictionary (note that for the imaging data this is going to be a second validation needed to ensure the quality of data). The Data Validation module validates the metadata associated with the imaging files identified by the user for submission against the data dictionary. If everything is OK, the Data Validation module creates a submission ticket and submission package. After that data are good for uploading. If errors are found, the module provides a detailed report of any data discrepancies, errors, and warnings. The module runs as a Java Web Start application locally on a user's computer (Java runtime environment is required).
Read more ...
The Data Validation module can be accessed via Data Repository > Validation Tool menu - TBD.