Changes

__NOEDITSECTION__[[Image:IM cycle.png|300px|center]] The After standardising auxiliary data, the next step in setting up IMSMA^NG {{IMSMANG}} is to customise implement the necessary customisation of the database reflecting the identified data elements that are trackedrequirements. Using Information managers have the information about additional data fields documented possibility to modify the 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 IMSMA^NGe. 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. IMSMA^NG does not automatically change data entry forms when data elements fields which are changedreferred to as Custom Defined Fields (CDFs).

Using the IMSMA^NG Data Inventory Manager, information managers can create new data elements or modify existing elements to map to their programme’s information needs. Because IMSMA^NG 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]].

[[Image:UserManual_DataInventoryManagerWindow.png{{Note |center|440px|''If there are many fields/CDFs in one category the Data Inventory Manager Window''may be slow to load. If that is the case then [[Move Fields Between Data Categories | move]]<div align="center">''Data Inventory Manager Windows''<fields/div>CDFs into a new or existing category.}}

{| class="wikitable"! colspan="2" | Icons in the Data Inventory Manager Window Modify Existing Fields==__NOEDITSECTION__|-! Icon! Description{{HowTo's|-[[Add values to enumeration list]]| [[Image:FieldTemplateIcon.pngChange Display Option for Single Select]]| Allows you to translate the selected terms.|-[[Translate enumeration lists]]| [[Image:UserManual_TranslateSelectedTermsIcon.pngAdd a Poly Property|Add a Poly Property]]| If an item is selected}}Using the Data Inventory Manager, adds a data category information managers can customise the values of existing enumeration lists to reflect local programme needs. Information managers can add new values to the selected itemenumeration lists and deactivate existing values.

If a data category is selected, adds a custom defined field to the selected category. |-| [[Image:FieldViewIconAdminGuide_ModifyingDataElements.png|center|500px|''Modifying Data Fields'']]| If a <div align="center">''Modifying Data Fields''</div> For example, the existing “Safety and Security Threat” data category is selectedfield for Land includes the values that are listed on the left side of the image. However, allows you to change information managers can deactivate the values that their Mine action programmes don’t use and add the data category namevalues that they do, as shown on the right side of the image.

If While adding and deactivating new values is an item attribute with customisable 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 fields, for example, the values is selected“Yes” and “No, allows you to add or remove custom option ” modifying these valuescan have unintended consequences.

If a custom defined field is selected, allows you to change the label or description. If the CDF is a multiple selection or single selection type, allows you to also change the selection values. |-| [[Image:EcksButton.png]]| Allows you to remove a data category.|-| [[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| Allows you to move the selected item attribute into a new or an existing data category. |-| [[Image:UserManual_CDFStatusIndicator.png]]| Allows you to change the status of a CDF between Active and Inactive. |}__NOEDITSECTION__==Create New Data ElementsFields==Information managers can create CDFs for those data elements not predefined in IMSMA^NG. IMSMA^NG 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__

|[[Data Categories|Data Categories]]|[[Add a Data Category|Add a Data Category]]|[[View Item Attributes Within a Data Category|View Item Attributes Within a Data Category]]|[[Change a Data Category Name|Change a Data Category Name]]|[[Remove a Data Category|Remove a Data Category]]|[[Move Item Attributes into a Data Category|Move Item Attributes into a Data Category]]|[[Filter Item Attributes|Filter Item AttributesCustom Defined Fields]]|[[Add Custom Defined Fields|Add Custom Defined Fields]]|[[View and/or Change Custom Defined Fields|View and/or Change Custom Defined Fields]]|[[Inactivate Custom Defined Fields|Inactivate Custom Defined Fields]]|[[Translate Custom Defined Field Labels|Translate Custom Defined Field Labels]]|[[Add a Custom Option|Add a Custom Option]]|[[Translate Custom Options|Translate Custom Options]]|[[Inactivate a Custom Option|Inactivate a Custom Option]]|[[Add a Poly Property|Add a Poly Property]]

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 IMSMA^NG{{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 in IMSMA<sup>NG<. How to translate the GUI is described '''[[Update the Localisation Files | here]]''' and how to translate the enumeration values and/sup> or CDFs is described '''[[Export the Translations | here]]'''. If the Mine Action programme needs to be multi-language e.g. Lao and some search options for eachEnglish then two different sets of Data Entry Forms may be developed or the Data Entry Form may contain labels in both languages.

[[Image:DataInventoryManager2.png|center|600px|'' Buttons in Data Inventory Manager Window'']]<div align="center">''Buttons in Data Inventory Manager Window''</div>

| '''Date/Time''' || Storage of dates, times or dates and times. Examples include Date of Accident and Data Entry Date[[Image:FieldTemplateIcon. png]]|| Is betweenIf an item is selected in the tree structure, a data category is before/afteradded to the selected item.

| '''Number''' [[Image:FieldViewIcon.png]]|| Storage of all numeric If a data category is selected, allows you to change the data used for calculationscategory name. Examples include Number of Ordnance and Total Population. || Equals, does not equal, is greater than/less than

| '''Text''' [[Image:EcksButton.png]]|| Storage of unstructuredIf a data category is selected, textual data. Text data can be as small as allows you to delete 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 descriptionscategory. || Is, contains, does not contain

| '''Pick Lists''' || 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 ! Right side|}</center> ===Dates, Text and Numbers===To create date, text and number fields in IMSMA^NG, 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 Data Entry Form and stored in the database}}  ===Pick Lists===Creating pick lists is one of the most powerful functionalities available in the IMSMA^NG Data Inventory Manager. Using this functionality, information managers can create rich data attributes for each IMSMA^NG 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 IMSMA^NG 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 IMSMA^NG 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}} ===Local ID Generators===IMSMA^NG provides a local identifier (local ID) data element for each item category or subcategory, which when used on data entry forms allows information managers to track items and Data Entry Forms entered into IMSMA^NG. These local ID data elements enable data entry clerks to click a button and insert an automatically generated ID rather than enter one manually, helping to reduce duplicate local IDs in the system.  IMSMA^NG comes with a default local ID type per item, but there is no limit to how many different types can be created. It is recommended to create at least one local ID type per item subcategory. For example, create a local ID type for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID types makes it easy to understand and find data. Local ID types are typically comprised of the following components: [Local ID Name]-[System Name]-[Incremented Number]For example, CR-HQ-1. {| class="wikitable"! Description

| '''Local ID Name''' |[[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| A text string that represents Allows you to move the item selected field(s) into a new or an existing data category or subcategory. For example, a completion report could be represented by “CR.”

| '''System Name''' |[[Image:FieldViewIcon.png]]| A value specified in the Client Configuration Tool of the IMSMA^NG TrayLauncher where system administrators can set If a separate multi- or single select system name for each installation of IMSMA^NGfield is selected, allows you to add or inactive enumeration values. For exampleIf a CDF is selected, allows you to change the label, description and display format. If the Headquarters installation could have “HQ” as CDF is a system name while a regional installation could have “R1multiple selection or single selection type, allows you to also change the selection values.”

| '''Incremented Number''' [[Image:FieldTemplateIcon.png]]|| A value that increases each time If a new ID category is generated. Information managers can specify the next number selected, adds a CDF field to be generated when the local ID generator button selected category.|-| [[Image:EcksButton.png]]| If a CDF is clicked. For exampleselected, a new local ID starting with CR-HQ-1 and proceeding allows you to CR-HQ-2 and so on will be generated each time the Completion Report local ID generator is clickeddelete unused CDFs.

{{NavBox Getting started with IMSMANG Administration}}[[Category:NAA]]