Phoenix can import datasets from files in .csv, .dat, .xpt, .sas7bdat, .xls, or .xlsx format. During the import process, a copy of the data is created. The original dataset file, no matter where it is located, is not altered by Phoenix in any way.
The maximum worksheet size Phoenix can import depends on the amount of RAM in the computer running Phoenix.
The following topics are discussed in this section:
Using the File Import Wizard dialog
See “ODBC Object” and “Watson Import” for other data importing options.
Note: When subject IDs with many digits are imported (e.g., 100010901), they are changed upon import to G8 format by default (e.g., 1.0001090E-08), even if they are imported as text. Using the G9 format preserves the subject ID digits. See “Set Microsoft .NET format string” for more information on numeric formats.
Note: Phoenix does not support line feeds within cells. The data may import correctly, but will not be handled consistently in the tools, and will not reload correctly after being saved in a project.
Using the File Import Wizard dialog
Options in the File Import Wizard dialog control how a dataset is imported into Phoenix. The File Import Wizard dialog is displayed when importing .csv, .dat. .xls, or .xlsx files.
Check the box(es) for the file(s) to import. Unchecked items will be ignored during the import.
Select a file in the list to view import options available for that file.
Depending on the type of file, the following options may be available:
Has header row: Check this box if a worksheet contains column headers.
Has units row: Check this box if a worksheet contains unit information for the column headers.
Has units in column header: Check this box if at least one of the columns in the worksheet has units included in the header. If checked, any characters that are after an underscore (_), within brackets ({}), or within square brackets ([]) in the source file will be considered as units for the column.
Treat consecutive delimiters as one: Check this box to have Phoenix treat two spaces, for example, as one space.
Field delimiter: Select the option buttons to indicate how the fields in a dataset are separated: by semi-colon, comma, space, tab, or a custom delimiter.
Missing value: If the dataset has a specific entry for instances where the value is missing, type that entry in this field. Any cells that match that entry will be left blank when they are imported. For example, a dataset may contain the word “None” in cells where a value is not available. Typing None in the Missing value field will import cells that contain the word “None” as a blank cell.
Start at row: Type the row number where importing is to start. The default value is 1.
Number of Rows to Import: Type the total number of rows in the dataset that are to be imported.
Preview the first 20 rows of data being imported, based on the currently selected options, in the Worksheet Preview tab.
Select the File Contents tab to view the first 20 rows of the raw file contents.
Select the Column Options tab to specify the data type of a column (Numeric or Text) and indicate any columns of data to ignore during the import (check the boxes in the Ignore column).
Note: The presence of non-numeric data in a numeric column can cause the type to switch to text. If this occurs, change the column type back to numeric.
Special characters in a .csv file may import incorrectly. If this occurs, save the .csv file as an Excel file and then import the .xls file.
Press Finish to import the file and display it in the viewing panel.
Or
Click Cancel to cancel the file import.
Phoenix file imports are controlled by the file extension. The extension determine where the file and any components are placed. The Custom Import menu forces a file to be imported as a binary, ASCII, or text file, without regard to the file extension. This menu is useful for importing file types that are recognized by Phoenix but do not contain data that is usable by Phoenix (e.g., attaching an Excel table to a project). By selecting File > Custom Import > Binary File the Excel file is placed in the Documents folder, and not in the Data folder.
Additionally, the Custom Import menu provides a way to import data for use with any of the third-party objects (e.g., R, SAS, PsN, etc.) as a shortcut.
Menu options include the following:
Binary File: Imported binary files are placed in a Documents sub-folder named after the imported file’s extension. For example, an imported .jpg file is placed in Documents/jpg. These files cannot be viewed or used in Phoenix. This menu option is best used to keep files in a project that are associated with a project but are not used directly in a project.
ASCII Data: Imported ASCII files are placed in the Data folder.
Plain Text: Imported text files are placed in the Code folder.
Shortcut: A shortcut object containing meta information about the selected file is added to the Shortcuts folder.