The document discusses various options for designing data entry forms and applications in CSPro, including: - Determining operating parameters like requiring operator IDs and allowing partial saves - The different file types used like .ent, .dcf and .fmf - Elements of forms like fields, text, boxes and backgrounds - Properties of fields including skip fields, persistence and uppercase text - Using rosters for repeated records - Specifying question text and conditions for computer-assisted personal interviewing - Adding extended controls for selecting options like radio buttons or dates on tablets

1. Creating Forms & Applications
P.Prabhu
Manager Research
5th August 2013

2. Data Entry Options
 Before designing forms, it is a good idea to determine the overall
operating parameters in which the program will run
 Some questions to answer:
– Do you want to know which keyer entered data into each file?
(operator id)
– Do you want to allow keyers to stop data entry in the middle of a
case, resuming keying later? (partial save)
– Do you want keyers to see a tree that gives details about the layout
of the questionnaire and allows the keyer to jump more easily to
previously keyed parts of the questionnaire? (case tree)
– Should the keyer be required to press Enter on each field before
the program advances to the next field? (require enter)

3. Data Entry Application Files
 .ent: the main file that pulls together all files needed for the data
entry application; this is generally the file you will want to open
 .dcf: the dictionary file
 .fmf: the form file
 .app: the logic for the data entry application
 .mgf: the message file
 .qsf: the CAPI question text file
 It is a good idea to show file extensions in Windows so that you can
properly identify each CSPro file

4. Forms
 A form is a collection of fields, text, and rosters (repeated items)
 A form may be larger than the screen; in these cases, the form
will scroll as necessary
 A form may repeat if it contains fields from a multiply-occurring
record
 Before you begin designing forms, it is good to have a plan as to
how many forms you need and the contents of each form
 Generally it is best to have one form for each record type

5. Form Elements
 Forms consist of:
– Freeform text
– Field-related text
– Fields
– Rosters
– Boxes
– Background color
 No form designed in CSPro will ever win a design contest, and
as such it is better to spend time testing the application rather
than making the forms pretty
 However, it is important that the forms are easy to understand
and navigate; usually a programmer tries to make the forms look
as close to the paper questionnaire as possible

6. Order of Execution
 To add a field to a form, drag it from the dictionary tree to the
form (or roster, if applicable)
 The order in which the fields are listed in the form tree is the
order in which they will be visited in the data entry application
 Move the fields up and down in the tree to modify the order of
execution

7. Rosters
 There are two options for adding multiply-occurring records to a data
entry application:
– Add the items to a repeating form; in this case, each occurrence of
the record will be displayed on a separate form
– Adding the items to a single form as a roster; in this case, values
for all occurrences will be visible on one form
 Rosters have the advantage that they generally look like their paper
questionnaires counterparts
 Forms with rosters can also contain fields from singly-occurring
records, which is not the case for repeating forms

8. Field Properties
 Skip field: In operator-controlled mode, pressing + will skip from this
field to the specified skip field
 Persistent: An ID item will automatically take the value found in the
previously entered case (at least one ID item must not be persistent)
 Sequential: The item will take the value of the previous occurrence,
incremented by 1
 Protected: The field cannot be keyed and must be assigned a value
with logic
– Note: Improperly-coded applications in which protected fields are
not assigned values will crash

9. Field Properties (continued)
 Upper case: Alphanumeric fields will be in all uppercase
 Mirror: Shows the value of an already-keyed field for reference
 Use Enter key: Forces the keyer to press Enter to advance to
the next field
 Force Out-of-range: Allows the keyer to input values not found
in the value set
 Verify: Should this field be verified in dependent verification?
 Capture type: Specifies a popup window “extended control” for
the field

10. Form Design Options
 Fields on forms can be aligned using the Align menu options
 Forms can be centered on the keyer’s screen (see Data Entry
Options)
 Modifying the Drag Options can simplify form creation
 Changing the default text and field fonts is one way to support
languages with non-Latin alphabets
 The background color of forms can be changed
 For simple dictionary testing, the Generate Forms command can
quickly create a working data entry application

11. Computer-Assisted Personal Interviewing
 In CAPI mode, question text appears in a window above the form
 Using the question text editor, the programmer can specify the text
for each field in the application
 Questions can be specified in multiple languages
 Different questions can appear depending on specific conditions
 Question text can be somewhat dynamic by including references to
other variables in the text, surrounding the variables by %s
– e.g., What is %NAME%’s sex?

12. Extended Controls
 In the new version of CSPro, 4.1, it is possible to have popup windows appear
that show the contents of an item’s value set
 For example, instead of having to key 1 or 2 for sex, a keyer can select the
proper radio button (Male/Female) with a mouse
 These controls are designed for CSPro use on tablets or other devices with
limited keyboard access
 In the CSPro designer, fields using controls have a blue border
 Controls include:
– Radio buttons
– Checkboxes
– Drop down boxes
– Date pickers

13. Thank you…
PSI