CAWI settings and modules are available under the Project menu whenever the "CAWI module type" has been selected in the Project Settings. The page is divided into two halves: the upper part for configuring the settings which apply to all CAWI modules, and the lower part for adding and configuring the CAWI modules themselves.
The above screen-shot shows the CAWI settings. They are presented in 4 sections: General, Browser and Cookies. the settings are described below:
|
Setting |
|
Description |
|
|
General |
|||
|
The maximum number of minutes that the screen can remain be idle, after which the session will be disconnected. |
|||
|
The number of simultaneous sessions that will be permitted. |
|||
|
Record Control |
|||
|
Allow more than one session |
Always |
If the cookie is detected, the respondent will be allowed to revisit the same survey (record) as many times as desired. |
|
|
Not Completed |
If the cookie is detected, the respondent will be allowed to revisit the same survey (record) provided that the survey has not been completed, i.e., the survey has not reached the Completion Question |
||
|
Never |
If the cookie is detected, the respondent will not be allowed to revisit the survey |
||
|
Browser |
|||
|
Open project in another window |
This option enables the questionnaire to be displayed in a new browser window. Unless selected, the other options for configuring the new browser window are inactive. Since the options are self-explanatory, they are not described here. |
||
|
Cookies Note: This will be in effect only if the cookie option in the respondent's browser is active. |
|||
|
Cookies Check Up |
This check-box controls whether Cookies are to be checked up |
||
|
Name |
A name for the cookie to override the name automatically generated by Interviewer Web. This field is optional. |
||
|
Expiration |
Number of days after which the cookie will expire i.e. the above options will not apply. |
||
|
Importation |
This check-box controls Cookie importation. Note: The cookie must be designed to designate the questions to receive the data, and the data which is to be written. The syntax is described in the topic "Creating a URL to access a project" under Importation of data into specified questions. |
||
|
Name |
Name of the cookie to be imported |
||
|
Domain |
The domain from which the cookie must have been originated |
||
The modules menu bar allows you to create new CAWI modules, and configure (edit) new or existing ones. The screen-shot below shows that a module has already been added; to view a module's configuration simply expand it by clicking on it ; to edit it you first click on it to select it, and then click on the Edit icon.
To the right of each collection module are commands for trying out the survey, deleting it, and stopping/activating it:
|
Setting |
|
Description |
|
Appearance |
Opens the Appearance Configuration page |
|
|
Test Questionnaire |
Runs the questionnaire which applies to the module. If no questionnaire is specified in the configuration for this module, the one specified in the Project Settings will be used. Note: When testing the survey no data will be written to the project database. |
|
|
Runs the questionnaire which applies to the module. If no questionnaire is specified in the configuration for this module, the one specified in the Project Settings will be used. Note:The survey will be run "live". A case record will be created or loaded according to the Sample Mode specified in the configuration; collected data will be written to the project database. The case launched can depend on the state of the Field i.e. call-backs, strata/quotas etc. |
||
|
Delete |
Deletes the collection module (does not delete the project). |
|
|
Stops an active collection module or activates a stopped collection module. |
||
The screen-shot below, taken while adding a new module, shows all of the settings for a CAWI collection module:
The settings are described below:
|
Setting |
|
Description |
|
The name for the collection module. Note: The name must be unique to the collection type within the Context i.e. it is not sufficient that it be unique to the project. |
||
|
A place on a designated web server where the questionnaire will be deployed and the survey conducted. See the Webspaces Overview. |
||
|
The questionnaire which will be deployed for conducting the survey. Note: If this questionnaire remains unselected, the questionnaire specified in the Project Settings will be automatically used instead. |
||
|
Soft Prompting is a questionnaire design feature, configurable on a question by question basis, which permits the respondent to proceed to the next question without selecting one of the choice codes offered. See Soft Prompting in Questionnaire Design. |
||
|
Survey User |
The username that the respondents must supply in order to access the survey. |
|
|
Survey Password |
The password (if applicable) that the respondents must supply in order to access the survey. |
|
|
Test: |
For testing. The survey will run without accessing the project database. |
|
|
New Record: |
A new record will be added to the project's data file each time a new case is dispatched. This is contrasted with the next option explained below. |
|
|
Restricted PIN Access |
Obliges a PIN number to be supplied in order to access the survey. This is usually given to the respondent by means of the link provided in the email sent to him/her. |
|
|
Use Sample: |
Cases are picked and dispatched from the project database according to the Field conditions and rules i.e. call-backs, quota conditions etc.. |
|
|
The language in which the agent interface will be presented. |
||
|
Start Page |
The complete path to the start page for the survey. |
|
|
End Page |
The exit URL for the survey. |
|