__NOEDITSECTION__[[Image:IM cycle.png|300px|center]] The After standardising auxiliary data, the next step in setting up {{IMSMANG }} is to customise implement the necessary customisation of the database reflecting the identified data elements that are trackedrequirements. Using Information managers have the possibility to modify the information about additional data fields documented database in Chapter 1, information managers can begin two ways:* modifying existing data fields and creating CDFsi. The objective of this step is to ensure that all data elements necessary for programme operations are available in IMSMANGe. This step must be completed prior to designing forms for data entry so fields that these changes exist in the database from installation which often are reflected on the referred to as system fields* creating new data entry forms. IMSMANG does not automatically change data entry forms when data elements fields which are changedreferred to as Custom Defined Fields (CDFs).
Using the IMSMANG Data Inventory Manager, information managers can create new data elements or modify existing elements to map to their programme’s information needs. Because IMSMANG comes with more than 1,000 data elements in its initial configuration, it The objective of this step is important to review these elements to determine if these adequately address the ensure that all data entry needs of the fields and values necessary for Mine action programmeoperation are available in {{IMSMANG}}. Where there are elements This step should be completed prior to designing Data Entry Form templates so that these changes are not included in the initial configurations, information managers can use reflected on the Data Inventory Manager to create themEntry Forms.
The {{note|{{IMSMANG}} does '''not''' automatically change Data Entry Form templates when changes are made in the Data Inventory Manager categorises all data elements by the type of item they belong to so that information managers can quickly navigate to the desired data elements.}}
The [[Image:UserManual_DataInventoryManagerWindow.png|center|600px|''Data Inventory Manager window lists all IMSMA item attributes and allows you to group the item attributes into meaningful categories. The Window'']]<div align="center">''Data Inventory Manager window also allows you to manage custom defined fields (CDFs) and custom options. Window''</div>
The ==Data categories==__NOEDITSECTION__{{IMSMANG}} comes with more than 1,000 system fields from installation and therefore it is important to search in the Data Inventory Manager window has two panes. The pane on the left displays before adding CDFs in order to [[Filter Item Attributes | determine if a data field already exists]] '''before''' adding it as a list of all items and the item attributes within themCDF. The pane on the right displays Data Inventory Manager shows the data field by item attributes in and [[Data Categories | sub-categories]] so information managers can quickly navigate and find the selected item or data category on the leftfields. It is also possible to [[Add a Data Category | add more categories]] and [[Add a Data Category | move fields between categories]].
[[File:{{Note | If there are many fields/CDFs in one category the Data Inventory Manager Windowmay be slow to load.png|440pxIf that is the case then [[Move Fields Between Data Categories |''Figure 140. Data Inventory Manager Window''move]]fields/CDFs into a new or existing category.}}
==Modify Existing Fields==__NOEDITSECTION__{{HowTo's|[[Add values to enumeration list]]|[[Change Display Option for Single Select]]|[[Translate enumeration lists]]|[[File:Icons in Add a Poly Property|Add a Poly Property]]}}Using the Data Inventory Manager, information managers can customise the values of existing enumeration lists to reflect local programme needs. Information managers can add new values to the enumeration lists and deactivate existing values. [[Image:AdminGuide_ModifyingDataElements.png|440pxcenter|500px|''Table 45. Icons in the Modifying Data Inventory ManagerFields'']]<div align="center">''Modifying Data Fields''</div> For example, the existing “Safety and Security Threat” data field for Land includes the values that are listed on the left side of the image. However, information managers can deactivate the values that their Mine action programmes don’t use and add the values that they do, as shown on the right side of the image.
[[File:Icons in While adding and deactivating new values is an effective and important capability within {{IMSMANG}}, information managers should approach changing the Data Inventory Manager Window text of existing values carefully.png|440px|''Table 45Because many values are used across different data fields, for example, the values “Yes” and “No,” modifying these values can have unintended consequences. Icons in the Data Inventory Manager Window'']]
==Create New Data ElementsFields==Information managers can create CDFs for those data elements not predefined in IMSMANG. IMSMANG does not limit the number of CDFs that can be created for each item; however, it is recommended that information managers use CDFs judiciously because the collection and management of unnecessary data is a substantial contributor to system performance and staff productivity issues in many programmes.__NOEDITSECTION__
{{HowTo's
|[[HowTo:Add a Data Category|Add a Data Category]]|[[HowTo:View Item Attributes Within a Data Category|View Item Attributes Within a Data Category]]|[[HowTo:Change a Data Category Name|Change a Data Category Name]]|[[HowTo:Remove a Data Category|Remove a Data Category]]|[[HowTo:Move Item Attributes into a Data Category|Move Item Attributes into a Data Category]]|[[HowTo:Filter Item Attributes|Filter Item Attributes]]|[[HowTo:Add Custom Defined Fields|Add Custom Defined Fields]]|[[HowTo:Add Subobject Custom Defined Fields|Add Subobject Custom Defined Fields]]|[[HowTo:View and/or Change Custom Defined Fields|View and/or Change Custom Defined Fields]]|[[HowTo:Inactivate Add Subobject Custom Defined Fields|Inactivate Add Subobject Custom Defined Fields]]|[[HowTo:Translate Custom Defined Field Labels|Translate Custom Defined Field Labels]]|[[HowTo:Add a Custom Option|Add a Custom Option]]|[[HowTo:Translate Custom Options|Translate Custom Options]]|[[HowTo:Remove a Custom Option|Remove a Custom Option]]
}}
Information managers can create CDFs for those data fields not predefined in {{IMSMANG}}. {{IMSMANG}} does not limit the number of CDFs that can be created for each item; however, it is recommended that information managers use CDFs sensibly because the creation of many CDFs is a substantial contributor to poor system performance. When determining new data elements fields to add to {{IMSMANG}}, it is important to carefully consider the types of data to be collected and the format of the data. Using the correct data type for each element field is critical to preserving the ability to search, calculate, sort and report information easily. ==Using {{IMSMANG}} in a different language than English==__NOEDITSECTION__{{IMSMANG}} provides the capability to translate and run the entire system in different languages. To fully translate the system into one or more languages, there are two parts to consider. The table below identifies GUI i.e. what the user see and the data types available . How to translate the GUI is described '''[[Update the Localisation Files | here]]''' and how to translate the enumeration values and/or CDFs is described '''[[Export the Translations | here]]'''. If the Mine Action programme needs to be multi-language e.g. Lao and English then two different sets of Data Entry Forms may be developed or the Data Entry Form may contain labels in IMSMANG and some search options for eachboth languages.
<[[Image:DataInventoryManager2.png|center>{| class="wikitable" width="600"600px|-'' Buttons in Data Inventory Manager Window'']]| <div align="center" colspan="3" | >'''Table 8. IMSMANG Buttons in Data Types'Inventory Manager Window''</div>{| class="wikitable"! Left side! Description
|-
| width="150pt" | [[Image:UserManual_TranslateSelectedTermsIcon.png]]| width="225pt" | '''Uses'''| width="225pt" | '''Search Options'''Allows you to translate the name of the categories.
|-
| *Date/Time* |[[Image:FieldTemplateIcon.png]]| Storage of datesIf an item is selected in the tree structure, times or dates and timesa data category is added to the selected item. Examples include Date of Accident and Data Entry Date. || Is betweenIs before/after
|-
| Report Owner [[Image:FieldViewIcon.png]]|| The If a data category is selected, allows you to change the data category name of the organisation that published the field report.
|-
| Version [[Image:EcksButton.png]]|| The version number that was assigned If a data category is selected, allows you to the field report when it was saveddelete a data category.
|-
| Key Dates - Initiated || The date on which the field report was approved. ! Right side! Description
|-
| Submitted |[[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| The date on which Allows you to move the selected field report was first submitted for approval(s) into a new or an existing data category.
|-
| Approved [[Image:FieldViewIcon.png]]|| The date on which If a multi- or single select system field is selected, allows you to add or inactive enumeration values. If a CDF is selected, allows you to change the label, description and display format. If the CDF is a multiple selection or single selection type, allows you to also change the field report was approvedselection values.
|-
| Approved by [[Image:FieldTemplateIcon.png]]|| The user ID of If a category is selected, adds a CDF field to the person who approved the field reportselected category.
|-
| Tabs - Field Report || Contains the data input field specified in the field report template[[Image:EcksButton.png]]|-| Reconciliation || Contains the location to which the field report If a CDF is associatedselected, the items associated with that location, and the item in the current field report. |-| Comments || Allows allows you to enter optional remarks concerning the field report. |-| Import Issues || Lists any problems that may have occurred when the field report was imported. This tab does not display if there are no import issuesdelete unused CDFs.
|}
</center>
Table 8. IMSMANG Data Types
Uses Search Options
Date/Time Storage of dates, times or dates and times. Examples include Date of Accident and Data Entry Date.
Is between
Is before/after
Number
Storage of all numeric data used for calculations. Examples include Number of Devices Found and Total Population.
Equals
Does not equal
Is greater than/less than
Text 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.
Is
Contains
Does not contain
Pick lists (single select and multiple select) 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.
Is in
Is not in
===Dates, Text and Numbers===
To create date, text and number fields in IMSMANG, information managers first select the type of item to create a CDF for and the type of CDF. Different types of fields make different operations available. For example, number fields enable calculations, date fields enable date searching and text fields enable text searching. After selecting the CDF, information managers provide a label and an optional description for the CDF.
{{note|Text fields are limited to a set number of characters. Larger amounts of data can be attached to a field report and stored in the database}}
===Pick Lists===
Creating pick lists is one of the most powerful functionalities available in the IMSMANG Data Inventory Manager. Using this functionality, information managers can create rich data attributes for each IMSMANG item that are searchable, translatable and customisable. Pick lists preserve data integrity by preventing problems associated with typographical errors, misspellings and other data entry errors, enabling users to compile and compare data easily. When created, the values for the pick lists can be modified to reflect changing needs over time.
Pick list data can be used in tools such as the Impact Scoring tool as well as in sorting and filtering. Data in single-select pick lists can be used to change the display of data on the map based on their values. For example, information managers can show different symbols on the map for different item attributes such as status, priority and type.
Creating a new pick list in IMSMANG requires information managers to first determine whether the pick list should allow the selection of single values (using radio buttons) or multiple values (using checkboxes). When this determination is made, the values for the pick list can be added and the pick list created. Information managers can also provide translations for the values, which automatically display for users running IMSMANG in other languages.
When the desired data elements are added to the Data Inventory Manager, information managers can proceed to form design to add the elements to the data collection forms.
{{note|* When creating single-select pick lists, information managers should include a “Not specified” value, which users can select when a more appropriate value is not listed. This option helps prevent inaccurate data from being added to the database.
* Single-select pick lists cannot be changed to multiple select pick lists}}
==Modify Existing Elements==
In addition to creating new data elements using the Data Inventory Manager, information managers can customise the values of existing pick lists to reflect local programme needs. Information managers can add new values to the pick lists and deactivate existing values. Deactivating existing values does not remove the values from the database nor does it change existing data or forms. Rather, it removes the options from the Source Tree in the Form Designer so that the values can no longer be added to new forms.
{{note|Deactivating or changing a value in the Data Inventory Manager does not change the forms that use the original value. Additional steps should be taken to prevent the original value from being used for data entry. These include updating and republishing all data entry forms that use the deactivated or changed value}}
For example, an existing “Mine Action Area Type” data element for hazards could include the values that are listed on the left side of the figure below. However, information managers can deactivate the values that their programmes don’t use and add the values that they do, as shown on the right side of the figure.
Figure 17. Modifying Data Elements
This lets information managers track the individual types of hazards they defined and documented in Chapter 1. Likewise, the ability to modify existing data elements gives information managers fine control over all the data elements they want to track in IMSMANG and how they are tracked.
While adding and deactivating new values is an effective and important capability within IMSMANG, information managers should approach changing the text of existing values carefully. Because many values are used across different data elements, for example, the values “Yes” and “No,” modifying these values can have unintended consequences.
{{note|It is preferable to add new values to pick lists and deactivate unnecessary elements than to modify the text of the value}}
==Manage Data Elements==
===Data Elements Groups===
All data elements in the Data Inventory Manager are grouped by item. When a data element is added to an item, it becomes an attribute of that item and cannot be moved to another item. However, information managers can divide data elements into subgroups for easier management. IMSMANG comes with several predefined subgroups for each item including an “Uncategorised” group. These groups are completely customisable and can be used to combine similar data elements, making it easier to find them during field report template design.
For example, an information manager can create a group of hazard data elements called “Used” that contains all data elements used in the local version of IMSMANG and another group called “Unused” that contains data elements not used by the programme. Another option for grouping data elements is by function. For example, an information manager can create a group called “Terrain Data” and include slope, vegetation and water feature data elements. A second group called “Impact Information” can contain data elements for the number of households impacted, the type of agricultural effects and blockages. By grouping data elements these ways, users browsing the Data Inventory Manager or designing data entry forms can quickly navigate to the elements they need.
===Data Elements Translation===
IMSMANG provides the capability to translate and run the entire system in different languages. To fully translate the system into one or more languages, there are two parts to consider. Information managers can translate the predefined data elements that come with IMSMANG and the CDFs they create or modify. IMSMANG stores translations for predefined data elements in editable properties files. Translations for all CDFs, including modified pick lists, are stored in the database and can be translated using the Data Inventory Manager. The translated values are available to all users connecting to the IMSMANG system and they can be exported using standard IMSMANG export functionality.
{{note|When running IMSMANG in a multilingual environment, translate CDFs and modified data elements immediately to make the translations available for form design and data entry. If the data elements are not translated, users only see the original values entered, no matter which language they have selectedNavBox IMSMA NG Administration}}[[Category:NAA]]