Decipher Expanded Variables Writeback - Naming Convention
Introduction
When writing data back to Decipher using the “Expanded Variables” writeback type, each code applied is written to a separate single variable in Decipher. This is in contrast to the “Dichotomous Variables” writeback type which creates a multiple question containing a separate binary value (i.e. column) for each code in the codeframe.
Some users prefer the “Expanded Variables” approach because it minimises the number of columns in exports and eliminates the “empty space” involved with the “Dichotmous Variables” approach.
However, the “Expanded Variables” approach will result in a variable number of questions being created in Decipher to store the coded data. The exact number of questions will vary depending on the number of iterations in the source data and the number of codes applied to each verbatim.
When Codeit creates these questions in Decipher, it follows a specific naming convention.
This page explains this naming convention.
Naming Convention
In short, the naming convention follows this pattern:
<Target Variable Name>[_oVerbatim Ordinal + 1][_cCode Index + 1]
To help understand what that means, let’s look at an example.
Simple Example
Suppose we have a set of verbatim data as follows:
ID |
Q1 |
1 |
Service, Price, Location |
2 |
Bad Service |
3 |
OK Service |
Suppose we code Q1 into a target variable called Q1_coded
If we just apply just one code to each verbatim then the naming of our output questions/columns in Decipher is straightforward:
ID |
Q1 |
Q1_coded |
1 |
Service, Price, Location |
12 |
2 |
Bad Service |
14 |
3 |
OK Service |
18 |
Multi-coded Example
But if we apply more than one code, then we need to generate a name for each of the additional codes, e.g:
ID |
Q1 |
Q1_coded |
Q1_codedc2 |
Q1_codedc3 |
1 |
Service, Price, Location |
12 |
7 |
8 |
2 |
Bad Service |
14 |
|
|
3 |
OK Service |
18 |
|
|
Multi-response Example
In addition to multi coding, we sometimes need to handle multi-response verbatims.
For example, suppose Q1 contains brand mentions where the respondent mentions up to 3 brand names, like so:
ID |
Q1 |
Q1 |
Q1 |
1 |
Brand A |
Brand B |
Brand C |
2 |
Brand B |
|
|
3 |
Brand X |
|
|
Since each respondent can give multiple answers to Q1, we again need a way of labelling the multiple outputs. Following the naming convention above, we would label the questions written to Decipher as follows:
ID |
Q1 |
Q1 |
Q1 |
Q1_coded |
Q1_codedo2 |
Q1_codedo3 |
1 |
Brand A |
Brand B |
Brand C |
10 |
25 |
6 |
2 |
Brand B |
|
|
25 |
|
|
3 |
Brand X |
|
|
9 |
|
|
Multi-coded, Multi-response Example
Lastly, sometimes we see a combination of multiple response data that needs to be multi-coded.
For example, suppose a respondent mentions two brands in one cell, like so:
ID |
Q1 |
Q1 |
Q1 |
1 |
Brand A;BrandX |
Brand B |
Brand C |
2 |
Brand B |
|
|
3 |
Brand X |
|
|
In this example, we would label the output data as follows
ID |
Q1 |
Q1 |
Q1 |
Q1_coded |
Q1_codedc2 |
Q1_codedo2 |
Q1_codedo3 |
1 |
Brand A;BrandX |
Brand B |
Brand C |
10 |
9 |
25 |
6 |
2 |
Brand B |
|
|
25 |
|
|
|
3 |
Brand X |
|
|
9 |
|
|
|