8.1 Script Overview

GEIS assumes that a survey script can be decomposed to discrete logically related items. An example of an item is a survey question. Note that some item types perform other functions that asking questions.

Any text editor can be used to create a script. A word processor can be used but must save the script as text. Ideally, macros can be used within the editor or word processor to aid in inserting item types in the script. For example, there should be a macro to insert a CHCE type, and another to insert a INFO type, etc. This greatly simplifies the process of writing a script.

Scripts must consist of a series of items with no blank lines between them. Some item types must appear in specific positions within a script. The permissible order of appearance of items is given in Table 5.

Table 5: Parts of a GEIS script in the order in which they must appear.

Script part	Function
TITL	The TITL must appear first. This sets the project title, assigns global options, and determines the interviewing mode.
SMSG	One or more SMSG items may follow the TITL item. A SMSG item is not required. When an interview starts these items display a message if the interview status code matches the item's status code.
SCAL	One or more SCAL items may follow the TITL and SMSG items. A SCAL item is not required in the script. They are used to define numeric or character constants within the script.
Interview	Any other item type may may appear next. The main body of the questionnaire is specified here.
STAT	The STAT item type appears toward the end of the script. The STAT items must follow all items that allow entry of respondent's answers, or which change data automatically. At least one STAT item that assigns a status code of CQ must be present in the script. Typically, there are several STAT items, one for each possible interview outcome. For example, CB for call-backs, DR for refusals, AM for answering-machines, ET for engaged numbers, and so on.
INFO	The final items in the script must not change the data. Typically, the last few items are INFO types used to thank the respondent, give final instructions to interviewers, and indicate that the end of the interview has been reached.

The script development process is illustrated in Figure 20. The steps are as follows:

1. Write the script using a text editor. The examples provided will be of use here.
2. Import the script.
3. Read the import error messages to determine syntax errors.
4. Correct the errors in the text editor.
5. Save the file.
6. Start again at step 2 if errors were found.
7. If no errors, open the compiler window.
8. Set any compiler options, if needed.
9. Compile the script.
10. Open the log window.
11. Scan the log for error messages to determine script logic errors.
12. Correct the errors in the text editor.
13. Start again at step 2 if errors were found.
14. If no errors, run the interviewing system.
15. Start an interview.
16. Proceed through each possible pathway through the script to pilot-test the script. It is important to thoroughly pilot-test the script according to local conventions.
17. If there is an error preventing jumping GEIS will stop and display the message:

    ``Unable to jump. Check item and prior items answered!''

    The system log will show the name and value of the item. Sometimes, this item will not be one of those that displays a question, such as TIME.
18. If a jump error occurs or some other modification is needed, correct the script in the text editor.
19. Start again at step 2 if errors were found.
20. Once all errors are eliminated and you are satisfied with the script you can proceed with the survey.

Figure 20: The script development process.