<?xml version="1.0" encoding="utf-8"?>
<html>
<span style="font-size:medium;">
<strong>Applicable Releases:</strong> caArray 2.0 and above
<strong>Date entered:</strong> 04/01/2009
</span>
caArray Usage
questionDiv
question}}Question: caArray Status of Importing: Imported vs Imported Not Parsed {{questionEnd
Browsing through NCI's caArray experiments, I noticed that the status for array design files and for experiment data files can be either "Imported" or "Imported (Not Parsed)". What are the differences between these two states (see figure 1)?
questionDivEnd
<noinclude>
\ width="100%" style="border: solid 1px #A3B1BF; background: #F5FAFF" |
- |
answer}}Answer:{{answerEnd
Imported and Imported (Not Parsed) describe the import status for array design files and for sample-related array data or annotation files (See File Supported by caArray). All images and experiment-level related information should be added to Supplemental Files.
File Import vs. File Parsing
Depending on the type of import, there are two stages to the adding a file to caArray: importing and parsing.
All files being imported pass through the "importing" state. It is a pure data storage process: the data file uploaded will be stored into the caArray database in its original data format (as it is).
If the files submitted are supported by caArray (see File Supported by caArray), they will be further parsed into a caArray table. During the file parsing, values from each data column, such as signal values, or log ratio values from an Affymetrix's CHP file, are extracted into a file-type specific table structure in caArray and associated to probe sets. These parsed files will be marked as Imported at the end of process.
caArray has the ability to upload the array design files or experiment data from many array providers, even if it doesn't have a parser available yet. Those files will ONLY be imported into caArray, without being validated or parsed. The end state of those files is imported not parsed as shown in Figure 1. Even if a file is not parsed, the user will still be able to download its contents (through caArray's user interface as well as through the programmatic API), and associate the file to samples, extracts and hybridizations. This caArray feature allows data to be shared and help the system identify which new parsers are needed to be developed in the future.
File Upload Process # 1: Array Design files
Figure 2 illustrates the data flow of how the array design files are processed in caArray.
File Upload Process # 2. Non Array Design Files
Figure 3 summarizes the general data flow for uploading a file into caArray. It depicts when a file should be loaded as a supplemental file and when it would be imported, either with a final status of Imported or Imported Not Parsed.
Have a comment? Please leave your comment in caArray End User Forum
</html>
