Default Codeit Export Naming Scheme
Introduction
The default export naming scheme is the original naming scheme used by Codeit when exporting variables.
It was originally implemented with 3 key objectives:
- If a variable is imported into Codeit, the original labelling should be retained and re-applied to the data on export.
- If a variable is created in Codeit (usually the case for target variables) the label generated should be based on the associated source variable name (if any)
- When exporting to Decipher, a more terse and compact naming scheme should be used
When exporting data, Codeit will generate a label for each variable as follows:
-
Imported Variables
When a variable has been imported into Codeit, the original labels provided on import are retained and reapplied to any file exports.
This mechanism applies even if a variable has been created by nesting a set of import fields. The labels for each nested field are retained and reapplied on export.
-
Created Target Variables - Mapped
If a target variable has been created by Codeit and is mapped to a task, Codeit will generate a column header according to this pattern:
If the associated source variable has labels defined (e.g. because the variable was imported):%Source Variable Label%%Target Variable Suffix%Element Explanation Optional %Source Variable Label% The original label used when importing a source variable No %Target Variable Suffix% The suffix defined in company settings to denote a target variable No
-
If the associated source variable does not have labels defined (e.g. because the variable was created in Codeit):
%Source Variable Name%_%Loop%_%Order%%Target Variable Suffix%%MulticodeIndex%Element Explanation Optional %Source Variable Name% The text name of a variable being exported. For more details see here. No %Loop% Denotes a specific Loop iteration index within a variable Yes - If a variable does not use Loop nesting, then this element will be omitted %Order% Denotes a specific Order index within a variable Yes - If a variable does not user Order nesting, then this element will be omitted %Target Variable Suffix% The suffix defined in company settings to denote a target variable No %MulticodeIndex% Denotes a specific Multicode index within a variable Yes
- If a variable does not have a codeframe attached, then this element will be omitted
- If the Multicode Export Type of a coded variable is set to "Concatenated" then this element will be omitted
- If the Maximum Codes Allowed setting of a variable is set to 1 then this element will be omitted
- If the Maximum Codes Allowed setting is not set, but the data being exported only contains a maximum of one response, then this element will be omitted.
-
Created Target Variables - Not Mapped
If a target variable has been created by Codeit and is not mapped to a task, Codeit will generate a column header according to this pattern:
%Target Variable Name%_%Loop%_%Order%%Target Variable Suffix%%MulticodeIndex%Element Explanation Optional %Source Variable Name% The text name of a variable being exported. For more details see here. No %Loop% Denotes a specific Loop iteration index within a variable Yes - If a variable does not use Loop nesting, then this element will be omitted %Order% Denotes a specific Order index within a variable Yes - If a variable does not user Order nesting, then this element will be omitted %Target Variable Suffix% The suffix defined in company settings to denote a target variable No %MulticodeIndex% Denotes a specific Multicode index within a variable Yes
- If a variable does not have a codeframe attached, then this element will be omitted
- If the Multicode Export Type of a coded variable is set to "Concatenated" then this element will be omitted
- If the Maximum Codes Allowed setting of a variable is set to 1 then this element will be omitted
- If the Maximum Codes Allowed setting is not set, but the data being exported only contains a maximum of one response, then this element will be omitted.