404
edits
Changes
no edit summary
After the Data Inventory Manager is customized to include all the necessary elements for data collection, the next step is to create field report templates. The Field Report Template Designer provides the capability for information managers to create customised field report templates for use with IMSMANG. The primary purposes of this tool are to:
1. Pick which data elements to collect for a programme
2. Design templates for data entry that mimic paper forms
{{HowTo's
|[[HowTo:Access the Field Report Template Designer Window| Access the Field Report Template Designer Window]]
==Design Concept==
The Field Report Template Designer is a “what–you-see-is-what-you-get” (WYSIWYG) application for creating data entry forms in IMSMANG. With its drag-and-drop capability, the Field Report Template Designer lets information managers select from all of the data elements available in the Data Inventory Manager and position them on a template. Information managers can create wholly new data collection forms and forms that mimic existing paper forms using only the data elements that are valuable to their programme’s workflow. The resulting, streamlined templates—free from tabs and other confusing navigational concepts—can then be printed and used for data collection.
Because the design process is critical to the proper functioning of the information management system, IMSMANG provides several capabilities to facilitate the design and sharing of field report templates. Information managers can save drafts to the file system prior to publishing. These drafts stored in .FFML format can then be exchanged with other IMSMANG users or IMSMANG systems and be used to design other templates so information managers do not have to start with a blank template.
{{note|* After creating field report 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 field report 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}}
===How It Works===
Figure 18. Process for Preparing and Maintaining Field Report Templates
The figure above shows how field report templates are prepared and maintained. Using the Field Report Template Designer, information managers build templates from the data elements in the Data Inventory Manager. The templates become the data entry screens for field reports. Information managers can design as many or as few templates as they desire, and they can save drafts or publish the templates as needed.
When a template is completed and ready to be used for data entry, information managers publish the template for use by data entry personnel. (Only published templates can be used for data entry.) Data entry clerks can choose the published template to enter data on, which, when approved in the system, permanently preserves the information. So, information managers can define not only the field report templates but also the format the information is displayed in when the data is approved.
Information managers can also remove or deactivate templates so they are no longer available for data entry, a capability that is particularly useful when older versions of a template needs to be replaced.
Several important principles of template design assist information managers in building effective templates. These include using data elements for one item per template, creating one template for each step of the workflow, including standard data elements on all templates, allowing only cosmetic changes to text labels, removing unnecessary elements from templates and using the text tool for instructions and versioning. Following these principles, information managers can achieve the correct balance of usability and data quality necessary for a well functioning programme.
===Use Data Elements for One Item Per Template===
While the Field Report Template Designer allows information managers to include data elements from more than one item on a single template (for example, hazard data elements and hazard reduction data elements), it is recommended to have data elements from only one item per template. Limiting the type of information collected on each template reduces the complexity of the reconciliation and approval process and helps ensure data quality and integrity. If a programme, for example, wants to use a general survey that collects information about hazards, hazard reduction activities and accidents, it is advisable to consider creating three independent general survey templates–General Survey-Hazard, General Survey-Hazard Reduction and General Survey-Accidents–rather than creating one comprehensive template for all aspects of the general survey.
Additionally, although a useful data element may exist for one item, avoid taking shortcuts and using that data element on a template for another item. Instead, consider creating a CDF for the second item rather than mixing and matching data elements from other items.
===Create One Template for Each Step of a Workflow===
As discussed above, each template should be reserved for one purpose to reduce the complexity and length of the template. In addition to using data elements for one item per template, information mangers should create one template for each item subcategory in a workflow. For example, a hazard reduction workflow could include separate templates for the different items, including a CHA and minefield, and activities, including a technical survey, clearance, progress report and completion survey.
While several of the templates may share similarities (for example, CHA and minefield), a separate template for each workflow step allows information managers to customise the templates to include only the information necessary for that step in the workflow. For example, all of the Mine Action Area Type values except for “Suspected Hazardous Area” could be removed from the CHA template, whereas all of the values except “Minefield” could be removed from the minefield template. This example is shown in the figure below.
Figure 19. Example of How to Limit Templates to Include Relevant Information Only
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 hazard workflow, a completion survey may be submitted that creates a hazard reduction to mark the end of clearance operations on a hazard. In this case, it is necessary to update the status of the hazard from “Worked On” to “Closed.” By using a template with only a handful of fields for status updates (like Local ID, Date of Report 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===
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 IMSMANG.
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
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.
Table 10. Other Useful Data Elements
Item Data Element Item Data Element
Hazard Name
Mine Action Area Type
Status
Area Size
Priority Victim First Name
Last Name
Gender
Age
Date of Birth
Killed/Injured
Victim Type
Hazard Reduction Name
Start Date
End Date
Type of Activity
Organisation
Status
Ordnance Found
Hours Spent
Size of Area
MRE Start Date
End Date
Organisation
[MRE Detail ID
MRE Type
% Male
% Female
Audience Number
Audience Age Info
Accident Date of Accident
Accident Type
QM Start Date
End Date
Organisation
Results
===Make Cosmetic Text Changes Only in the Field Report Template Designer===
Like the Data Inventory Manager, the Field Report Template Designer provides the capability to modify the text of existing data elements. This includes creating and editing labels, changing fonts and sizes and editing pick list values. This functionality can be used to ensure templates are laid out correctly and represent a programme’s data needs. Using this functionality in the Field Report Template Designer, however, should be limited to performing cosmetic changes only, and should not be used to change the meaning or substance of a text element. Cosmetic changes include:
Cosmetic change Example
* Abbreviating text “Number” to “No.”
* Adding instructions “Pick one of the following:”
* Correcting misspellings “Anml” to “Animal”
* Translating terms “Mines to “Minas”
Using the text changing functionality in the Field Report Template Designer to change the substance or meaning of a text label or value can cause serious confusion and data quality problems. Examples of problematic or dangerous substantive changes to text during template design include changing:
Existing text Substantive change
* “Number of Mines” “Number of Clearance Teams Recommended”
* “% Female” “Number of Females”
* “Heavy” “Flail” (for the type of mechanical device recommended)
Any substantive change to a data element should instead be made in the Data Inventory Manager, either by editing an existing data element or by creating a new CDF.
===Remove Unnecessary Elements from Field Report Templates===
By removing unnecessary or invalid choices from forms, information managers can improve the quality of data collected and entered into IMSMANG. For example, if a form is designed to be a Minefield form, then there is no need to keep other possible values for the “Mine Action Area Type” that are not “Minefield.” In this case, values such as “SHA,” “Dangerous Area” and “Other” can be removed from the form, leaving “Minefield” as the only possible choice. This helps improve data quality while reducing the size and complexity of data entry forms.
===Use the Text Tool for Instructions and Versionning===
Using the Text Tool in the Field Report Template Designer, information managers can add text to data entry forms independently of other data elements. This allows information managers to add additional instructions to field report templates to help improve the quality of data entry. These instructions can include simple statements such as “Choose only one” or longer sentences such as “If the reported date occurs before January 2010, enter the following...” The Field Report Template Designer even supports paragraphs or lists of instructions as needed.
Additionally, information managers should include versioning information on field report templates. By creating a simple versioning system and displaying the version number on the template (as shown below), it is easy to determine whether information is being entered on the current version of the template or a previous version.
Figure 20. Example of a Version Number on a Field Report Template
==Template Publishing==
When the field report templates are designed, information managers can publish them for use. The publication process includes choosing an organisation that the template belongs to and providing a version number. When an individual template is designed to support the needs of a specific organisation, information managers can select the organisation as the owner of the template. For example, if organisation XYZ uses a specific template to collect information, the template can be assigned to XYZ when it is published. Note that setting the owner of the template does not restrict data entry personnel from using the template. The template that is published and assigned to XYZ is accessible to all IMSMANG users, not just XYZ personnel. Also, if a template is for general use or not designed to support a specific organisation, the owner of the template can be set to “IMSMA” or any other organisation created in IMSMANG.
When a template is published using the same name as another published template, IMSMANG automatically deactivates the previously published template. Note that this does not change the format of any data already entered into IMSMANG using the previously published template. IMSMANG preserves the integrity of data as it was entered. Subsequent field reports, however, are entered and displayed using the updated version of the template.
To ensure the most recent and useful templates are available for data entry, information managers should periodically review the status of the published templates and deactivate or delete any templates no longer needed. If a template has already been used to enter data into IMSMANG, the template cannot be deleted from the system. But, information managers can deactivate the template so it cannot be used for data entry. Templates that have not already been used can be deleted.
==Translating Templates (Multilingual Environment)==
When running IMSMANG in a multilingual environment where different users run IMSMANG in different languages, information managers have two options for creating templates:
* creating multilingual templates
* creating multiple versions of each template
Either approach works successfully and gives users of multiple languages full access to IMSMANG data.
===Multilingual Templates===
Figure 21. Example of a Multilingual Field Report Template
===Multiple Versions of Each Template Types=====Field Reports====Admin Forms==An alternative approach to template design is to create a separate version of the same template for each language. Benefits of this approach include reduced form size since each piece of text is only represented once and simplified template creation since users can change their locale settings and begin designing templates that take advantage of the translations already provided in IMSMANG.
