callweb.cgi - doccati

home features DOCUMENTATION pricing contact us
technical documentationCATI documentationcookbook robot

Appendix A

CATI Project initiation checklist

The following checklist is offered as a guide to control that all steps of the project installation process have been completed.

Edit the BASEprojets project to document the new project; make sure the project is labelled "active".

Edit the BASEpasse project to ensure that each interviewer has a user ID.

Insert a PRESTRATE question in the questionnaire.

Ensure that the PRESTRATE question text segment lists each active stratum along with the maximum number of cases that can be used from the sample in each case, as in 1=50, 2=100, 3=200 if the intent is to limit the number of cases used from stratum 1 to 50.

Insert a CALCTESTQUOTAS question in the questionnaire.

Ensure that the CALCTESTQUOTAS is a CALCUL question which defines the TESTQUOTAS question, as is TESTQUOTAS = $PRESTRATE.

Insert a TESTQUOTAS question in the questionnaire.

Ensure that the TESTQUOTAS syntax is respected:

the "complete" parameter should be the name of a question which will systematically contain something in completed questionnaires and systematically be empty in incomplete questionnaires; typically, the "complete" question is a BLANK question which is only accessed as part of a completed questionnaire;

the "skip" parameter should be the name of a question where cases beyond quotas are sent to display a Sorry message and terminate the interview; typically, the "skip" question is a CULDESAC and BACKWALL question which is only accessed as part of a quota-filled questionnaire; using display conditions or skips, make sure that the quota-filled cases do not have a value in the Complete question (unless quota-filled cases do constitute a complete case);

each active quota must be listed, along with the target number of completion as in 1=50, 2=100, 3=200 if the intent is to complete 50 questionnaires in stratum 1.

Make sure that there is one field in the questionnaire for each field that must be pre-populated. Plan to pre-populate non-numeric data with at most four digits into the main part of the question; other types of data must be pre-populated into the open-end part of the question. Ensure that the pre-populated fields which must be displayed to the interviewers are given an INFOCATI type.

Create a subdirectory in the CallWeb directory to store the project files. Prefix the subdirectory name with "cw" so that CallWeb recognizes it as a project directory. Give read and write permissions to "the world" and to the owner on that directory.

Copy a call result code file (.ccw) from another project into the project directory and name it according to the project name ("project.ccw").

Carefully review each result code in cwcodescati.cgi to ensure that the associated behaviours are appropriate for the current project; add new codes or delete old ones according to the requirements of the project.

Compile the project and ensure that there were no compilation errors. Correct errors and re-compile.

If appropriate, create an HTML page called "consigne.html" containing general instructions to interviewers and/or the contact text and place it in the project directory.

Create a tab-delimited file of data to be pre-populated which includes, at a minimum, for each case, the _telkey, the _telephone field and group membership in PRESTRATE.

Make sure that the first line of the file identifies correctly the field to be pre-populated: think through whether the main part or the open-end part of a question needs to be fed the data.

The simplest way to create this tab-delimited file is to use Excel to build a spreadsheet including the required calculations and to save the sheet as a "tab-delimited" file from within Excel.

Send the pre-population data file to the server and perform the pre-population.

Using cwnav.cgi, verify that the data were pre-populated as expected.

From the supervisor menu, add telephone numbers to the list accessible to interviewers.

Enter the number of New numbers to be made available.

Make sure to include all categories of results that should be automatically brought back to the attention of the interviewers on a regular basis (e.g., busy, no answer, but probably not fax and not in service).

Make sure to request automatic updates at least every 20 minutes.