Instructions

android

Introduction

Creating a project

Form Builder

Adding a Form
          Key Field
          Title

Text Fields
          Plain

          Numeric
          Date
          Time
          Drop-Down
          Radio 
            Check Boxes
          
Media Fields
           Location

           Photo
           Video
           Audio
           barcode

Validation
           Text
           RegEx   
           Double Entry

Form Logic
           Jumps


Linking Forms
           Hierarchy

           Branching

android


Installing EpiCollect+
Loading a Project


Collecting Data

Text Fields
          Plain
          Numeric
          Date
          Time
          Drop-Down
          Radio
             Check Boxes

Media Fields
           Location

           Photo
           Video
           Audio
           barcode

Saving Data

List/Sync data

Maps

Backing up data

Remote Data

Settings

android


Project Website

Map View

Multiple Forms

Downloading Data

android


Introduction

EpiCollect Markup

The Document
           <model>

The Form
           <form>


Text Fields
           <input>

          <select>
           <select1>
          <radio>
Setting defaults

Media Fields
           <location>
           <photo>
           <video>
           <audio>
           <barcode>

Defining keys

Form Logic
           Jumps


Linking Forms
           Hierarchy

           Branching
  
Validating



Collecting Data - Text Fields

 

Any text field is available for you to use any number of times when defining a project form (see Form Builder instructions). We will now indicate what a user sees when presented with each type of text field, prior to moving on to media fields.

Please note: musch of this is covered within the Form Builder documentation, however we also present here for clarity.

Plain Text Field

When a user is presented with a plain text field, the devices soft keyboard is launched automatically allowing them to enter free text before progressing to the next question, as in the following screenshots:

location1

 

 

 

 

arrow

 

 

 

 

 

location2

 

 

Required fields

If the text field is a key field or has been defined to be 'required' then a user will be warned if they try to progress in the form without entering data as in the following screenshots:

location1

 

 

 

 

arrow

 

 

 

 

 

location2

Key Fields are always required as they define the unique data field for a form.

Additionally, if a user attempts to enter a key field which is identical to a previous entry, they will be warned.

When we progress to describing synching data to a server we will also describe how, a user cannot submit an entry where an entry already exists in the database (ie submitted by someone else) with the same key field value.

 

Double Entry Fields

If, within a form, the option 'double' has been specified, a user is required to enter the answer to a particular question twice. The values a user has entered are checked against eachother and if they differ, the user is warned. In the following screenshots we are attempting to enter two different email addresses (first screenshot). On attempting to progress in the form, the user is warned that the 'values are different'. Tapping OK allows the user to change the values prior to progression in the form.

location2

 

 

 

 

arrow

 

 

 

 

 

location2

 

 

 

 

arrow

 

 

 

 

 

location2

Note: Similar validation and user warnings occur when a text field has had a regular expression added to it in the Form Builder. More information of regular expressions can be found here.

We will now describe a user entering a numeric field

 

Next | Numeric Fields