The Reporting Field Tree is a series of nested menus which organize survey fields. The Field Tree's options are driven by the selections made in the Reporting Field Selector.
When By Chapter is selected, the nests only expand to the survey chapter level. When Individually is selected, the nests expand further, all the way down to the single field level. Each chapter can be expanded or minimized to display or hide the list of fields within a chapter by clicking the +/- symbol to the left of the chapter name.
There are five default chapters that appear in every survey, in addition to the custom chapter additions made via survey programming. These chapters are:
Chapter | Description |
Record data | Contains fields with information about respondents start and end times, status, and the testmode flag. |
Survey fields | Contains the user-defined chapters and all other data fields, e.g., question widgets, standard quotas, etc. This is the default home for user-created survey data. |
Appendix |
Contains two sub-chapters by default: Device data, which stores various information about respondent hardware used to take the survey, and Field Management, with quota variable metadata, in addition to feedback, page, and interview time information. All derived quotas created with |
System fields | Contains many other additional system-generated auditing and calculating fields. For a list of default system fields, see Default system variables. |
Managers only fields | Contains fields that can only be viewed by Managers and Survey Owners. By default, the fields panel_quota , entry_url , and final_redirect are added to this sub-chapter. |
Tip! In r8.1+, the panel
variable is no longer assigned to the Managers Only chapter and will instead be located in the Record data chapter.
The Field Selector may also include a User-defined fields chapter in the Field Tree. This chapter is added if users have added fields that were not defined in the survey source, such as respondent specific identifying data, or creating weights to apply in reports and data cuts.
For additional information on creating weights, see Using weights.
Comments
0 comments
Please sign in to leave a comment.