Jump to: navigation, search

Standardising Data Entry Forms

85 bytes added, 18:10, 11 February 2014
Version 6.0
* After creating Data Entry Form templates in {{IMSMANG}}, it is recommended to use another application to build the same forms for handwritten data collection in the field. The templates are built to accommodate typewritten data which requires less space than handwritten data. Using templates to record data in the field may impose limitations on the amount or extent of information collected.
* When a general layout and design is determined for a programme’s Data Entry Form templates, it is a good idea to save an .FFML file to the file system so it can be used as the basis for designing the rest of the programme’s templates. This should be done prior to adding item-specific data to the template.
<li>Determine the layout of the Data Entry Form template. This includes the Data Entry Form template’s paper size, paper orientation, and margin sizes.</li>
<li>Add report data fields to the Data Entry Form template. Report data fields include Date of ReportInformation, Report Form ID, and Reported By.</li>
<li>Add item attributes for which you would like to capture data to the Data Entry Form template. You can also add images, lines, text areas, and scribe panels to the Data Entry Form template.</li>
<li>Arrange the elements on the Data Entry Form template. You can change the data element labels, move the data elements, and align the elements. </li>
Information managers should also consider creating a template designed to update the status of each item when administrative changes to items may be required. For example, in a typical land workflow, a completion survey may be submitted that creates an activity to mark the end of clearance operations on a land. In this case, it is necessary to update the status of the land from “Worked On” to “Closed.” By using a template with only a handful of fields for status updates (like Local ID, Date of Report Information and State), an information manager can ensure that all items of a customised workflow are updated properly and with minimal effort.
===Include Standard Data Elements on All Templates===__NOEDITSECTION__
| width="300pt" | '''Rationale'''
| align="left" | Date of Report Information || align="left" | A data element used in summary calculations and for searching for Data Entry Forms by the date they were created
| align="left" | Report Form ID || align="left" | A local ID that provides a unique identifier for searching for and displaying Data Entry Forms in the Workbench
| align="left" | Item ID (for example, Land ID) || align="left" | A local ID that provides a unique identifier for searching for and displaying Data Entry Form items in lists
| width="200pt" | '''Data Element'''
| align="left" | Land || align="left" | Name,Land Classification,
Area Size,
Ordnance Found,
Hours Spent,
Size of Area
| align="left" | Education/Education Detail|| align="left" | Start Date,
End Date,
Education Detail ID,Education Type(Education Detail), % Male(Education Detail), % Female(Education Detail),Audience Number(Education Detail),Audience Age Info(Education Detail)
| align="left" | Accident || align="left" | Date of Accident,

Navigation menu