Browse
 
Tools
Rss Categories

Question types

Reference Number: AA-01604 Last Updated: 2017-07-18 13:42

When designing a survey, you can add questions of different types. The currently supported question types are:

Note: All question types support the Required constraint

Instruction

Use an instruction when you simply wish to display information to the fieldworker. Instructions can also form placeholders for enhanced survey controls.

Select Questions

Select question types require you to configure a list of options. You can choose whether the user can choose one option (single select) or many options (multiple select).

Options consist of two components: a label and a code or valueThe label is displayed to the fieldworker, while the value is stored and exported. Try to keep values as short as possible (preferably numeric) to reduce data transfer. 

For example:



When creating options, the number to the left indicates the question order, the value in brackets indicates the coded value and the detail between is what is shown on the handset

An example of what it would it would look like on the device can be found here.

Text Questions

Text questions allow the user to capture any textual input - including numbers, letters and symbols. The different sub-types simply determine how the field will appear (not supported by all devices):

  • Single line - suited to small amounts of input
  • Multiline, free text - suited to larger amounts of input
  • Predictive - legacy support for feature phones

For example:


The question on the device would look like this.

Text questions support the Must Equal and the Match constraints.

Numeric Questions

Numeric questions allow the user to capture numeric inputs only. You can choose whether decimal inputs will be allowed or only whole numbers.


The question on the device would look like this.

Numeric questions support the Inequality, Must equal, Range and Match constraints.

Formatted Input

Formatted questions types allow for the answers to be applied to the desired format and allow for easy entry and accurate data due to the built in order applied validation.

Examples are:

Date input: Enter the required text and the formatting is handled on the back end.


The question on the device would look like this.

Various forms of validation can be applied in conjunction with operators (the response must not equal today's date) or can be simply specific by using the constraints calendar available, see below:


Time: A formatted input for allowing specified times to be applied.

These can be in the following 3 formats if noted on the question text:

  1. Time of day - AM/PM
  2. Time of day - 24 hour format
  3. Length of time in hours.

The question on the device would look like this.

Phone number: Numeric type field that allows for 10 digits or more to inserted.

Validation can also be inserted to ensure a valid South African mobile number is inserted:


GS1 identifier: The question type confirms that the last digit of a bar code number is a computer check digit which makes sure the bar code is correctly composed.



Password: Allows for letters and numbers to be entered but hides the input as you type.



Email address: Allows an email format (letters, numbers and characters) to be inserted.


PIN: Allows for the entry of a numeric PIN code where the output is hidden.



Numeric identifier: Allows for longer strings of numbers to assist in validating formats such as ID numbers.


Validation can be added, for example, to confirm the number is a valid South Africa ID number:


Multimedia 

Photo Capture: Allows for the capture of photos.


The question on the device would look like this.

Advanced 

GPS: Allows for the capture of GPS co-ordinates


The question on the device would look like this.

Variable: A question type that can be hidden and store various formats of data. It also allows for operators to be implemented, including enhanced survey controls such as the Option List Hierarchy.

For example, here is a household calculation using variables and operators:




Rss Comments
  • There are no comments for this article.