Author > Activating questionnaires > Activate Current Project: Participants settings > Uploading participant records > Required fields for personal interviews
 
Required fields for personal interviews
Active
Set to 1 while the sample management functions are running; that is, while the record is in the ACTIVE queue.
Data type and length: Long
Null permitted: Yes
Primary key: No
Default value: 0
ActivityStartTime
The StartTime of latest record in the history table for a specific sample.
The session engine will update this value for the latest activity on the sample record.
Data type and length: DateTime
Null permitted: Yes
Primary key: No
Default value: Null
AppointmentTime
The time in UTC at which the respondent asked to be called.
For disconnected samples, UNICOM Intelligence Interviewer - Offline for Windows needs to update this value after the interviewer sets up an appointment time with the respondent.
Data type and length: Date
Null permitted: Yes
Primary key: No
AssignedInterviewerId
The field manager sets this value as the interviewer ID for distributing participant records.
Data type and length: Text(64)
Null permitted: No
Primary key: Yes
Audit
Records changes made to other fields (except Comments) in the record.
Data type and length: Text(2000) but see Notes for more information
Null permitted: Yes
Primary key: No
CallOutcome
The contact outcome (return) code for the previous call to this record.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Comments
Additional information about the participant. Interviewers may update this field when they call or contact the participant.
The standard multimode sample management scripts display records with comments before dialing so that the interviewer can read the comments before talking to the participant.
Data type and length: Text(2000) but see Notes for more information.
Null permitted: Yes
Primary key: No
DistributedTo
The interviewer ID or IDs to which the participant is distributed.
Data type and length: Text(64)
Null permitted: No
Primary key: Yes
ExpirationTime
Defines the participant record expiration date and time. For example, a project may dictate that participant records can only be called or contacted within a specific date range.
Expired records are not available for dialing (except for retrieving appointments).
Data type and length: DateTime
Null permitted: Yes
Primary key: No
Default value: 2099–12–31 23:59:000
Id
The sample record ID that uniquely identifies each sample record.
Data type and length: Text(64)
Null permitted: No
Primary key: Yes
InterviewMode
Written to by the sample script to record which interview mode was used for a particular interview: is set to Web for an inbound self-completion interview, Phone for outbound telephone interviewing, or Personal for personal interviewing. In projects that allow a mix of inbound and outbound calling, the sample management script will set this field.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
PreviousInterviewerID
The name of the interviewer who last contacted the participant. This allows appointments to be returned to the previous interviewer if the current time is before the AppointmentMarginAfter interval has passed. Appointments that are not kept within this period may be passed to any interviewer.
When interviews are reviewed, this field is updated with the name of the reviewer.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
PreviousQueue
The name of the queue in which the record was previously held. When records are displayed for interviewers, the record's current queue is always shown as ACTIVE because the record has been selected for interviewing.
Displaying the value of PreviousQueue can be useful to interviewers as it may provide additional information about the record's calling history. For example, if PreviousQueue is FRESH, the interviewer knows the record has not been called before, whereas if PreviousQueue is APPOINTMENT, he/she knows that the respondent has already been contacted and has asked to be called back to be interviewed.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Queue
Names the queue in which the record is currently held.
When replicate identifiers are defined in the queue field for specific records, those records can then be used to create sample/participant record subsets.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Default value: FRESH
ReturnTime
The time at which the record was returned to sample management. This allows you to specify the amount of time that must elapse between repeat contacts to records whose interviews timed out or were stopped.
Data type and length: Date
Null permitted: Yes
Primary key: No
Screener
Identifies which respondents are the suitable candidates for the current survey. Screener questions are designed to filter respondents. If a respondent answers do not meet the Screener criteria, the respondent is not allowed to continue the survey, and the Screener field is recorded as Failed. If respondent answers meet the Screener criteria, they are allowed to continue the survey, and the Screener field is recorded as Passed.
This field can be set using the following IOM script in routing (it is the data source for the Incidence report).
Passed Screener:
IOM.SampleRecord.Item
["Screener"].Value =
"Passed"
Failed Screener:
IOM.SampleRecord.Item
["Screener"].Value =
"Failed"
IOM.Terminate(Signals.
sigFailedScreener, True)
In order to accurately calculate the project incidence, the Screener field is added to the sample table. The field is updated during the survey with three values – Null, Passed, and Failed. The sum of Passed is the incidence numerator; the sum of Passed and Failed is the incidence denominator. The incidence report is generated using TOM based on the data source, sample table, and sample history table.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Default value: Null
Serial
The unique serial number that UNICOM Intelligence Interviewer - Server Admin assigns to each respondent's case data. Generally, this serial number is not the same as the sample record ID. When a respondent restarts an interview, UNICOM Intelligence Interviewer - Server Admin uses the serial number to retrieve the respondent's case data record and to display the responses (stored in the case data record) that the respondent has already given.
Data type and length: Long
Null permitted: Yes
Primary key: No
Default value: 0
SortId
A random value that can be used for sorting records prior to selection. (Appointments and recalls are not affected by this property as they are always sorted in ascending date/time order.) This value can prove useful in personal interviewing when planning the contacts for the day as SortIds can be manually edited and then used for sorting in the Interviewer window to show the visit order. The Participants activity can initialize this field with a random value when uploading records. If records are uploaded in batches, each record in the sample table receives a new random number, not just those being uploaded in the current batch. See "Naming the Database Server, Sample Database, and Sample Table" in the UNICOM Intelligence Interviewer - Server Admin User's Guide for details.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Default value: Null
Test
Set to 1 if the record is test data, or 0 if it is real data (also known as live data). This column is used by the Interviewing activity to restrict the type of data that appears in phone reports. If the value is Null, the Interviewing activity will treat the record as if it is both real and test data.
Data type and length: Long
Null permitted: Yes
Primary key: No
Default value: Null
TimeZone
The respondent's timezone. This is used in the setting of appointments to ensure that any time differences between the respondent's and interviewer's locations are taken into account when the record is presented for recalling.
Data type and length: Long
Null permitted: Yes
Primary key: No
UserId
The UserId of latest record in the history table for a specific sample.
Data type and length: Text(64)
Null permitted: Yes
Primary key: No
Default value: NULL
See also
Uploading participant records