Changes

Standardising Data Entry Forms

1,363 bytes removed, 21:39, 18 February 2013
no edit summary
<li>Design templates for data entry that mimic paper forms</li>
</ol>
 
{{HowTo's
|[[HowTo:Access the Field Report Template Designer Window| Access the Field Report Template Designer Window]]
|[[HowTo:Share Field Report Templates|Share Field Report Templates]]
}}
 
==Design Concept==
Some data elements should always appear on field report templates to preserve data integrity and searchability. By standardising these data elements, information managers ensure that the elements at a minimum can be used to find data within IMSMA<sup>NG</sup>.
Table 9. Standard Data Elements
 
Data Element Rationale
Date of Report A data element used in current view calculations and for searching for field reports by the date they were created
 
Report ID
A local ID that provides a unique identifier for searching for and displaying field reports in the Workbench
 
Item ID
(for example, Hazard ID) A local ID that provides a unique identifier for searching for and displaying field report items in lists
 
Geographical Reference
A table for adding geospatial information about field report items for displaying the items on the map
<center>
{| class="wikitable" width="600"
|-
| align="center" colspan="2" | '''Table 9. Standard Data Elements'''
|-
| width="300pt" | '''Data Element'''
| width="300pt" | '''Rationale'''
|-
| align="left" | Date of Report || align="left" | A data element used in current view calculations and for searching for field reports by the date they were created
|-
| align="left" | Report ID || align="left" | A local ID that provides a unique identifier for searching for and displaying field reports in the Workbench
|-
| align="left" | Item ID (for example, Hazard ID) || align="left" | A local ID that provides a unique identifier for searching for and displaying field report items in lists
|-
| align="left" | Geographical Reference || align="left" | A table for adding geospatial information about field report items for displaying the items on the map
|}
</center>
The table below lists other useful data elements to include on data entry forms. Most of the data elements are predefined in the Data Inventory Manager.
<center>{| class="wikitable" width="650"|-| align="center" colspan="4" | '''Table 10. Other Useful Data Elements'''|-| width="125pt" | '''Item ''' | width="200pt" | '''Data Element '''| width="125pt" | '''Item '''| width="200pt" | '''Data Element'''|-| align="left" | Hazard || align="left" | Name
Mine Action Area Type
Status
Area Size
Priority | align="left" | Victim || align="left" | First Name
Last Name
Gender
Killed/Injured
Victim Type
|-| align="left" | Hazard Reduction || align="left" | Name
Start Date
End Date
Hours Spent
Size of Area
| align="left" | MRE || align="left" | Start Date
End Date
Organisation
[MRE Detail ID
MRE Type
% Male
Audience Number
Audience Age Info
|-| align="left" | Accident || align="left" | Date of Accident
Accident Type
| align="left" | QM || align="left" | Start Date
End Date
Organisation
Results
 
<center>
{| class="wikitable" width="600"
|-
| align="center" colspan="3" | '''Table 8. IMSMANG Data Types'''
|-
| width="150pt" |
| width="225pt" | '''Uses'''
| width="225pt" | '''Search Options'''
|-
| '''Date/Time''' || align="left" | Storage of dates, times or dates and times. Examples include Date of Accident and Data Entry Date. || align="left" | Is between
Is before/after
|-
| '''Number''' || align="left" | Storage of all numeric data used for calculations. Examples include Number of Devices Found and Total Population. || align="left" | Equals
Does not equal
Is greater than/less than
|-
| '''Text'''|| align="left" | Storage of unstructured, textual data. Text data can be as small as a few characters or as long as several paragraphs. Text elements are good for storing data that cannot be stored in other formats, such as comments or narrative descriptions. || align="left" | Is
Contains
Does not contain
|-
| '''Pick lists (single select and multiple select)''' || align="left" | Storage of structured data where values must be confined to certain pre-defined choices. Ideal for structuring data for searching, reporting and translating. Examples include Type of Activity and Terrain. || align="left" | Is in
Is not in
|}
</center>
0
edits