Data Entry > UNICOM Intelligence Interviewer > Interviewer Console window > Case List > Case List rows
 
Case List rows
A Case List row represents a single interview that has, at the very least, begun entry. Each row is identified by a respondent ID. The respondent ID can be automatically added by UNICOM Intelligence Interviewer when the project is configured by the project author during activation. The respondent ID can also be a specific ID that is entered based on an identifier that is allocated to a specific interview.
Note When the project includes sample data, the rows represent participants and case entry my not yet have begun.
For more information about configuring the respondent ID during Activation, see the UNICOM Intelligence Professional User’s Guide.
Rows are added to the Case List when you:
create a new case (see Creating a new case)
import case data that was forwarded to you by another operator (see Importing case data).
To open an existing case and continue entry, or edit entries that are already saved, double-click on the row in the Case List to launch the appropriate UNICOM Intelligence Interviewer entry player. For more information, see Reopening a case for data entry.
If you are performing data entry, and your UNICOM Intelligence Interviewer installation is configured for multi-user verification keying, you are only be able to verify cases that you did not key during the case’s Initial Entry pass. If you are working in a project or batch, that includes cases that you keyed in the Initial Entry pass, you will not be able to view or access those cases when the Entry Mode is set to Full or Partial Verification. For more information, see Entry modes and Case List behavior.
Rows can also be removed from the Case List when you:
delete a case (see Deleting a case)
create and deploy a data package (see Creating a data package for deployment). For cases keyed in Live Interviewing mode, all active cases are included in a data package. For cases keyed in Data Entry, data packages are made from whole batches. When a batch is included in a data package for deployment, the batch and all of its associated cases are removed from the Case List.
See
Case List