Does ATLAS.ti Mac allow SPSS export?

April 19, 2018

Good news! ATLAS.ti Mac 8.2 and higher lets you export your entire project as SPSS syntax file. Another option is to export all data as Excel spreadsheet for further analysis in  other statistical packages like R, STATA or SAS.

ATLAS.ti is intended primarily for supporting qualitative reasoning processes. On the other hand, especially with large amounts of data, it is sometimes useful to analyze the data using statistical approaches. ATLAS.ti can export your data in form of a *syntax* file for SPSS®, and a generic Excel format that can be imported to packages like R, SAS, STATA as well as SPSS.

The basic components for statistics are cases and variables. The statistic export function in ATLAS.ti treats codes as variables and data segments (quotations) as cases.

In contrast to the dichotomous treatment of codes within ATLAS.ti, you can use codes for further statistical analysis as ordinal or interval scaled variables by using a specific code-naming convention.

The notion of a “case” here is rather fine-grained and differs from the common understanding of this term. Usually cases in qualitative research refer to persons, interviews, or documents. We chose to treat the smallest unit as a case for the statistical export, to ensure that no data is lost. Broader information, e.g., which document or document group a quotation belongs to, is coded into the various variables.

Scaled and Dichotomous Codes

Within ATLAS.ti, a code is always *dichotomous*, because it either refers to a given quotation (“1”), or it does not (“0”). Each case (= quotation) can, in respect to the codes, be described as a vector of 0’s and 1s. The concept of scaled codes/variables requires a special syntax.

If you for instance want to code for three different levels of evaluating something: very good, good, neither god or bad, bad, very bad, A special naming convention (name%value) is necessary to let ATLAS.ti identify scaled codes from dichotomous codes. When coding the data, the code category needs to look as follows:

EVALUATION

+ evaluation%1 very bad
+ evaluation%2 bad
+ evaluation%3 neither good or bad
+ evaluation%4 good
+ evaluation%5 very good

This notation allows the system to construct *one *variable from all codes with the same prefix. The variable name will be “evaluation”, and the values for this variable are:

+ 1 very bad
+ 2 bad
+ 3 neither good or bad
+ 4 good
+ 5 very good

Instead of the % as separator, you can also choose a different separator.

Share this Article