Overview
SurveyToGo allows you to import Dimensions MDD scripts including the routings. When later exporting the data back to DDF the SurveyToGo platform will automatically fill in some of the Dimensions system variables. This article describes the system variables populated and which SurveyToGo variable is mapped to which Dimensions system variable.
Dimensions System Variables mapping
The following table shows the SurveyToGo variables that are automatically pushed to the relevant Dimensions system variables:
| MDD System Variable | SurveyToGo variable | Comments |
| Respondent.Serial | SubjectID / InterviewID | This field will get populated with the SurveyToGo interview ID. It is on purpose that we use the Serial and not the respondent ID as we would not want to cause any conflict with existing respondent ID's in the Dimensions system collected by Dimensions for the project. |
| Respondent.ID | DeviceIndex ( = Global Index in the Operations Console) | This variable shows as DXXXXXX-YYY and represents the unique id of the interview generated during the run of the interview |
| DataCollection.Removed | FALSE | Hardcoded |
| DataCollection.Status | {complete} | Hardcoded, will be changed in future versions to support SurveyToGo filtered interviews as well |
| DataCollection.InterviewerID | Surveyor Name (string) | The SurveyToGo Surveyor Name field. |
| DataCollection.StartTime | VisitStart | Click here to learn more about the various date fields captured by SurveyToGo and what they mean. |
| DataCollection.FinishTime | VisitEnd | Click here to learn more about the various date fields captured by SurveyToGo and what they mean. |
| Datacollection.EndQuestion | Does not relate to any SurveyToGo variable | Will contain the variable name of the last question visited. |
Comments
Please sign in to leave a comment.