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

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

The time in UTC at which the respondent asked to be called.

Data type and length: Date

Null permitted: Yes

Primary key: No

The number of calls or contacts made to this record after an appointment was set. When sample records are uploaded into the sample table, a non-null default value should be specified otherwise errors will occur during the upload.

Data type and length: Long

Null permitted: Yes

Primary key: No

Default value: 0

Records changes made to other fields (except Comments) in the record.

This field was new in UNICOM Intelligence Interviewer - Server Admin 4.0. In earlier versions, these changes were stored in the Comments field.

If you reuse a pre-v4.0 sample table that contains a Comments field of SQL type ntext, the Audit field is created as nvarchar(2000) instead. This is due to an issue in the Microsoft OLE DB consumer templates that prevents a table containing two ntext columns.

Data type and length: Text(2000)

Null permitted: Yes

Primary key: No

The call outcome (return) code for the previous call to this record.

Data type and length: Text(64)

Null permitted: Yes

Primary key: No

The number of call recordings for this record. Records loaded with this field empty have this field set to Null in the sample table.

Call recording is an option when a telephone interviewing project uses an autodialer.

Data type and length: Long

Null permitted: Yes

Primary key: No

Default value: 0 for telephone projects, otherwise Null

Additional information about the participant. Interviewers may update this field when they call or contact the participant.

In pre-v4.0 sample tables, the Comments field is created as ntext(16). If you reuse a pre-v4.0 sample table that contains a Comments field of type ntext, its data type remains unchanged and the Audit field is created as nvarchar(2000) instead. This is due to an issue in the Microsoft OLE DB consumer templates that prevents a table containing two ntext columns.

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

The number of times that the number has been connected. This field is updated when a sample is auto-dialed and connected.

Data type and length: Long

Null permitted: Yes

Primary key: No

Default value: 0

Records the call count for each specific day part.

For example, assume there are two day parts named aa, ab. The value for this field will be aa1|ab2 (or aa1). This means the sample was used to call one time in aa time range and two times in ab time range. If the sample has not yet been used, the value of this field is null.

Data type and length: Text(128)

Null permitted: Yes

Primary key: No

Default value: Null

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

The sample record ID that uniquely identifies each sample record.

Data type and length: Text(64)

Null permitted: No

Primary key: Yes

Used in conjunction with a 3rd party dialer. In full predictive mode, this field should accompany all numbers dialed commands. It is set to an initial value by the CATI system for the first dialer (for a different dialer, the initial value can be different).

SPSS Dialer will return a new value for Internal Dialer Flag for the number. After dialing, this field will be updated with the new value, and this value will be permanently set with the sample record and passed through for all subsequent dialing attempts.

Data type and length: Text(64)

Null permitted: Yes

Primary key: No

Default value: NULL

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

How many times this sample has been called and received NoAnswer. This field is updated when a sample is dialed and returned with a call outcome of NoAnswer

Data type and length: Long

Null permitted: Yes

Primary key: No

Default value: 0

Must contain a phone number if the record is to be used for telephone interviewing.

If the project uses an autodialer, phone numbers that start with a + sign will have that character replaced by the InternationalAccessCode defined in DPM. + signs preceded by white space or other characters are not replaced.

If the project allows inbound calling, you can add a question to the script that asks respondents to enter contact numbers, and then update the sample records with this information.

Data type and length: Text(64)

Null permitted: Yes

Primary key: No

The name of the interviewer who 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

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

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

The time in UTC that was set as the callback time for appointments that are set automatically by the sample management script.

Data type and length: Date

Null permitted: Yes

Primary key: No

Indicates that the record must be manually dialed. The sample management script will set AutoDial=0 for these records.

The feature will not work if RequiresManualDial is not defined in the participants table.

Data type and length: Long

Null permitted: Yes

Primary key: No

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

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

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).

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

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.) 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

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

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

If sample records are used in telephone interviewing projects, you can use the TrunkGroup field to specify which trunk group of the dialer will be used for dialing the sample record. If you want the dialer to automatically select the trunk group, the field should be set to NULL or empty.

Data type and length: Long or Text(64)

Null permitted: Yes

Primary key: No

Default value: NULL

The number of calls made to this record. When sample records are uploaded into the sample table, a non-null default value should be specified otherwise errors will occur during the upload.

Data type and length: Long

Null permitted: Yes

Primary key: No

Default value: 0

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