• <GetStart>
  • CSPro User's Guide
    • The CSPro System
    • Data Dictionary Module
    • The CSPro Language
    • Data Entry Module
      • Introduction to Data Entry
      • Data Entry Application
        • General Data Entry Concepts
        • CSPro Data Entry Concepts
          • Operator vs. System Controlled
          • Data Entry Path
          • Data Entry Elements
          • Blocks
          • Issues to Consider When Designing a Form
          • Tips on Reviewing Data Entry Applications
        • Create a Data Entry Application
        • Change Data Entry Characteristics
        • Forms Designer
      • Data Entry Editing
      • CAPI Data Entry
      • Network Data Entry
      • Android Data Entry
    • Batch Editing Applications
    • Tabulation Applications
    • Data Sources
    • CSPro Statements and Functions
    • Templated Reporting System
    • HTML and JavaScript Integration
    • Action Invoker
    • Appendix
  • <CSEntry>
  • <CSBatch>
  • <CSTab>
  • <DataViewer>
  • <TextView>
  • <TblView>
  • <CSFreq>
  • <CSDeploy>
  • <CSPack>
  • <CSDiff>
  • <CSConcat>
  • <Excel2CSPro>
  • <CSExport>
  • <CSIndex>
  • <CSReFmt>
  • <CSSort>
  • <ParadataConcat>
  • <ParadataViewer>
  • <CSCode>
  • <CSDocument>
  • <CSView>
  • <CSWeb>

Issues to Consider When Designing a Form

If you plan to key data from paper questionnaires you generally try to make the forms (screens) match the paper questionnaire layout—however if you will be capturing data using CAPI, the layout is less important. Whichever mode of entry is used, the following rules regarding what can be dropped on a form will apply.
Single or Multiple?
The structure of the data dictionary will impose limitations if any of the records or items repeat (are "multiple"). Dictionary elements are multiple if:
  • A record is considered multiple if it is defined as "Max > 1" in the data dictionary.
  • An item is considered multiple if it is defined as "Occ > 1" in the data dictionary.
  • A subitem is considered multiple if it has been defined as "Occ > 1" in the data dictionary OR if the item it belongs to is defined as "Occ > 1".
Dropping Dictionary Elements
Keep in mind the following rules when you design your data entry forms:
  • You can mix ID items with items from single records on the same form.
  • You can mix items from different single records on the same form.
  • You can split items from the same record onto different forms, whether or not the record repeats.
  • You can make more than one roster from a multiple record. The rosters can be on the same form or on different forms. For example, if you have numerous person-level questions, you could place core items from the record (name, relationship, sex, age, and marital status) into one roster and put the remaining person-level record items onto a second roster.
  • You can mix items from a single and a multiple record on the same form, but the latter must be in a roster.
  • You cannot mix items from different multiple records on the same form.
  • You cannot mix items from different levels on the same form (applies to complex data dictionaries only).
If you have any multiple records, items, or subitems in the data dictionary, you must decide whether you want to make them into a roster or use a form that repeats. You must take this into account when deciding which items to place on each form.
Cases and Levels
A case is the primary unit of data in the data file. A case usually corresponds to a questionnaire, although some complex applications may have a hierarchical set of questionnaires that comprise a single case. For example, the main questionnaire may consist of a household roster and other household information, and there may also be a separate questionnaire for each woman in the household.
The data entry application may then contain two levels—one for the household and one for each woman in the household. The set of forms corresponding to the household make up level one. The set of forms corresponding to each woman make up level two. Each case would consist of a level one and a variable number of level occurrences for level two. Most applications consist of a single level.