Introduction

The Data Entry component of Enter fulfills the module's primary function: the collection of data entered into the fields of a questionnaire and the storing of that information in the project's database.  The data collected depend on the fields placed on the questionnaire during Form Layout.  The process of collection is administered by Check Code.  As data are entered, the cursor moves between fields according to the Tab Order and any (potentially data-dependent) deviations ordered by the underlying Check Code commands.  Data are automatically saved when moving to a new page and when navigating to a new record or another existing record.  If the user attempts to exit before the data are saved, the user is stopped and prompted with an opportunity to do so.

Open Enter

Objective

Given a form populated with fields and supporting check code (and an initialized database, see Section 3.2.1.1.4), open the form in Enter to enter data.

Preconditions

The user shall have a .prj file containing a project with a form with information about its variables and layout.

Postconditions

The completed form is open in Enter, ready to accept the addition of a new database record. 

Stimulus/Response Sequence

Functional Requirements

1. The system shall enable the user to:
   1. open Enter from the main menu,
   2. use Enter either a standard or full screen mode, and
   3. browse the file system from Enter in order to locate and open a project and form for data entry.
2. The system shall enable the user to switch: 
   1. from Enter to Form Designer, keeping the same project, form, and page open,
   2. from Enter to Visual Dashboard, keeping the same project and form data open for analysis, and
   3. from Enter to Map, keeping the same project and form data open for analysis.
3. The system shall provide a shortcut that allows the user to open one of the last four forms opened previously.
4. The system shall prompt the user to: 
   1. create the data table(s) in the database when opening a form that has been created but not yet initialized,
   2. close a form while Enter continues to run,
   3. exit the Enter module,
   4. preview and print a form with data,
   5. preview and print one or more forms populated with data records,
   6. compact the database.

Create Records and Enter Data

Objective

Using the Enter component of Epi Info™ 7, the system shall enable the user to add a new record to a form and enter data into that record.

Preconditions

Enter is running.  A project containing a form is loaded. The cursor is positioned at the first field, according to the form's Tab Order.

Postconditions

The fields of the form have been populated, creating a new record for that form in the project database. The record can be visualized in tabular format using any of the options available in the Line Listing menu.  The record will be given a serial "line" number for reference, visible on the button bar when the record is in focus and in the first column of a Line List table.  The record can be identified using Find and query on a specific field using the corresponding value from that Record.  If the user navigates away from the new record using the "|◄", "◄", "►", or "►|" buttons on the button bar, the record is automatically saved.

Stimulus/Response Sequence

Notes:

1. This table indicates when the commands in specific Check Code blocks would execute relative to other data entry events, assuming those blocks exist.  The code blocks themselves are optional.

Functional Requirements

1. The system shall enable the user to add data to the current record of the current form in the current project by:
   1. typing text or pasting it using Ctrl-V into Text, Text (Uppercase), and Multiline fields,
   2. typing numbers or pasting them using Ctrl-V into Number, Phone Number, Date, Time, and Date/Time fields,
   3. using a left-mouse-button click or spacebar on Checkbox and Option fields, and
   4. selecting an item from a pull-down menu in Yes/No, Grid, Legal Values, Comment Legal, and Codes fields.
2. The system shall enable the user to select an item from a pull-down menu by using one or more of the following methods:
   1. typing the initial letters of the item, 
   2. moving up or down the list using the arrow keys, 
   3. using the Enter key, and
   4. clicking with the left-mouse-button.
3. The system shall enable the user to navigate between fields by:
   1. using Tab to move to the next field in the Tab Order,
   2. using Ctrl-Tab to move to the previous field in the Tab Order, and
   3. using the mouse to select an arbitrary field with a left-mouse-button click.
4. The system shall enable the user to switch between form pages in the current record by:

   1. using Tab on the last field in the Tab Order on the page, and

   2. selecting the appropriate branch of the form tree in the pages frame.

5. The system shall save data automatically (provided that all required fields are satisfied) when:

   1. the user clicks on the New Record button,

   2. the user moves to another record by clicking the record navigation buttons,

   3. using Tab on the last field of a form, and

   4. the Check Code engine executes a NewRecord command.
6. The system shall enable the user to navigate to an arbitrary record by typing its number into the Current Record Number field, located on the button bar between "New Record |◄  ◄" and "of n €► €►|", and pressing the Enter key.
7. The system shall automatically populate the values for fields with the "repeat last" option set with the values from the last record viewed.
8. The system shall enable the user to populate an image field by clicking on the field and using the file browser, which opens automatically, to select an image to be save with the record.  
9. The system shall enable the user to mark records for deletion
   1. and "undelete" the marked records for the life of the project.
10. The system shall enable the user to modify data from previously entered records in fields on the open form.
11. The system shall enable the user to save modified data records.
12. The system shall enable the user to view and print a Data Dictionary consisting of a list of all variables in a form, including:
    1. variables associated with fields, and
    2. Permanent, Standard, and Global variables created by Check Code,
13. along with the following information about those variables:
    1. Page Position (page number), Page Name, Tab Index (indicating Tab Order), and Prompt (the previous information types not applicable for Permanent, Standard and Global variables),
    2. Field Type (Permanent, Standard, Global or one of the field variable types listed in Description of Form Elements),
    3. (Variable) Name,
    4. Variable Type (Boolean, Date, DateTime, Grid, Image, Number, Text),
    5. Format (e.g., ##.## for Number, ###-###-#### for PhoneNumber, YYYY-MM-DD for Date, optional in most cases) (not applicable for Permanent, Standard, and Global variables),
    6. Special Info (not applicable for Permanent, Standard, and Global variables) such as:
       1. "Read Only" or "Required",
       2. allowed value ranges for numerical variable, or
       3. name(s) of variables from fields aggregated into Groups.
14. The system shall enable the user to create a "package for data transport" that:
    1. prompts for a package name and path to store the package using Windows Explorer or 
    2. provides a field into which the path can be entered manually with an optional timestamp at the end of the package name,
    3. is optionally password protected,
    4. allows data to be removed from form fields,
    5. allows data to be removed from form grids,
    6. allows records to be selected for inclusion
       1. based on the evaluation of one or more expressions composed of <field_variable> <relational_operator> <value> joined by the logical operator AND;
       2. using one or more fields as "match keys",
    7. allows the data from one or more fields to be removed from all records, and
    8. allows specific columns to be removed from data grids.
15. The system shall enable the user to copy a shortcut to the clipboard for use in an icon on the desktop to quickly open the form in Enter.
16. The system shall enable the user to import data from:
    1. a mobile device,
    2. a Web survey,
    3. cloud data capture,
    4. an Epi Info™ 7 project, and
    5. a data package.