System generated files

October 1, 2019

Every archive of data exported from the Survey Solutions Headquarters contains among the user data the following system-generated data files:

The above data files are saved in the same data format as the main survey data, for example, if the main data is requested in Stata format, the system-generated data files will also be exported in Stata format.

The data files are also accompanied by an automatically generated text file named export__readme.txt. This file documents which version of the Survey Solutions software was used to export the data, when the export was done, and placement of variables into the data files. Here is an example of such a file that may be accompanying, e.g. an agricultural survey.

The contents of the system-generated data files is described in the table below:

assignment__actions

VariableTypeMeaningExample
assignment__idnumericUnique id of the assignment.6037
datestringDate when the action was taken2018-12-12
timestringTime when the action was taken10:11:12
actionnumericType of action taken. See assignment action codes.12
originatorstringLogin name of the person performing the actionJohnSup
rolenumericSystem role of the person performing the action. See role codes.2
responsible_namestringLogin name of the person now responsible for the interviewJackInt
responsible_rolenumericSystem role of the person now responsible for the interview. See role codes.1
old__valuestringValue that was changed (optional).3
new__valuestringNew value that was specified (optional).5
commentstringAny comment left by the action originator.Complete this assignment by Friday!

interview__actions

VariableTypeMeaningExample
interview__keystringInterview key (identifier in XX-XX-XX-XX format)12-34-56-78
interview__idstringUnique 32-character long identifier (GUID) of the interview.5b3c8288289646699580e16f5d1b6d1e
datestringDate when the action was taken2018-12-12
timestringTime when the action was taken10:11:12
actionnumericType of action taken. See action codes.12
originatorstringLogin name of the person performing the actionJohnSup
rolenumericSystem role of the person performing the action. See role codes.2
responsible_namestringLogin name of the person now responsible for the interviewJackInt
responsible_rolenumericSystem role of the person now responsible for the interview. See role codes.1

interview__comments

VariableTypeMeaningExample
interview__keystringInterview key (identifier in XX-XX-XX-XX format)12-34-56-78
interview__idstringUnique 32-character long identifier (GUID) of the interview5b3c8288289646699580e16f5d1b6d1e
roster\*stringName of the roster containing the variablemembers
id1\*numericRoster ID of the 1st level of nesting7
id2\*numericRoster ID of the 2nd level of nesting7
id3\*numericRoster ID of the 3rd level of nesting7
id4\*numericRoster ID of the 4th level of nesting7
variablestringVariable name for the commented questionage
ordernumericSequential order of the comment1
datestringDate when the comment was left2018-12-31
timestringTime when the comment was left12:34:56
originatorstringLogin name of the person leaving the commentJohnSup
rolenumericSystem role of the person leaving the comment. See role codes.2
commentstringText of the commentAge is confirmed by document

interview__diagnostics

VariableTypeMeaningExample
interview\_\_keystringInterview key (identifier in XX-XX-XX-XX format)12-34-56-78
interview\_\_idstringUnique 32-character long identifier (GUID) of the interview5b3c8288289646699580e16f5d1b6d1e
interview\_\_statusnumericLast status of interview. See status codes.100
responsiblestringLast responsible personJohnSup
interviewersnumericNumber of interviewers who worked on this interview1
rejections\_\_supnumericHow many times this interview was rejected by supervisors0
rejections\_\_hqnumericHow many times this interview was rejected by HQ1
entities\_\_errorsnumericNumber of questions and static texts with errors10
interview\_\_durationstringActive time it took to complete the interview, DD.HH:MM:SS00.05:28:39

interview__errors

VariableTypeMeaningExample
interview\_\_keystringInterview key (identifier in XX-XX-XX-XX format)12-34-56-78
interview\_\_idstringUnique 32-character long identifier (GUID) of the interview5b3c8288289646699580e16f5d1b6d1e
roster\*stringName of the roster containing the variablemembers
id1\*numericRoster ID of the 1st level of nesting7
id2\*numericRoster ID of the 2nd level of nesting7
id3\*numericRoster ID of the 3rd level of nesting7
id4\*numericRoster ID of the 4th level of nesting7
variablestringVariable name for the question, where validation error occurredage
typenumericType of the variable where the validation error occurred. See type codes.2
message__numbernumericNumeric index of the validation rule that has fired1
messagestringText of the error messageAge may not be negative

Fields indicated with a star (*) are optional and present only if the questionnaire template contains rosters.

Code tables

For coded variables in the system-generated data files the following tables outline the meaning of the codes:

Coding of roles
CodeMeaning
0<UNKNOWN ROLE>
1Interviewer
2Supervisor
3Headquarter
4Administrator
5Api User
 

Coding of assignment actions
CodeMeaning
0Unknown
1Created
2Archived
3Deleted
4ReceivedByTablet
5UnArchived
6AudioRecordingChanged
7Reassigned
8QuantityChanged
9WebModeChanged
 

Coding of interview actions
CodeMeaning
0SupervisorAssigned
1InterviewerAssigned
2FirstAnswerSet
3Completed
4Restarted
5ApprovedBySupervisor
6ApprovedByHeadquarter
7RejectedBySupervisor
8RejectedByHeadquarter
9Deleted
10Restored
11UnapprovedByHeadquarter
12Created
13InterviewReceivedByTablet
14Resumed
15Paused
16TranslationSwitched
17OpenedBySupervisor
18ClosedBySupervisor
 

Coding of interview statuses
CodeMeaning
-1Deleted
0Restored
20Created
40SupervisorAssigned
60InterviewerAssigned
65RejectedBySupervisor
80ReadyForInterview
85SentToCapi
95Restarted
100Completed
120ApprovedBySupervisor
125RejectedByHeadquarters
130ApprovedByHeadquarters
 

Coding of types
CodeMeaning
1Section
2Question
3StaticText
4Variable