Data Inventory Manager

After standardising auxiliary data, the next step in setting up IMSMA^NG is to implement the necessary customisation of the database reflecting the identified data requirements. Information managers have the possibility to modify the database in two ways:

modifying existing data fields i.e. data fields that exist in the database from installation which often are referred to as system fields
creating new data fields which are referred to as Custom Defined Fields (CDFs).

The objective of this step is to ensure that all data fields and values necessary for Mine action programme operation are available in IMSMA^NG. This step should be completed prior to designing Data Entry Form templates so that these changes are reflected on the Data Entry Forms.

	IMSMA^NG does not automatically change Data Entry Form templates when changes are made in the Data Inventory Manager.

IMSMA^NG comes with more than 1,000 system fields from installation and therefore it is important to search in the Data Inventory Manager before adding CDFs in order to determine if a data field already exists before adding it as a CDF.

The Data Inventory Manager shows the data field by item and sub-categories so information managers can quickly navigate and find the data fields. It is also possible to add more categories and move fields between categories.

Data Inventory Manager Window

	If there are many fields/CDFs in one category the Data Inventory Manager may be slow to load. If that is the case then move fields/CDFs into a new or existing category.

Modify Existing Fields

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.

	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 “Safety and Security Threat” data field for Land 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.

Modifying Data Fields

This lets information managers track the individual types of land they defined. Likewise, the ability to modify existing data fields gives information managers fine control over all the data fields they want to track in IMSMA^NG and how they are tracked.

While adding and deactivating new values is an effective and important capability within IMSMA^NG, information managers should approach changing the text of existing values carefully. Because many values are used across different data fields, for example, the values “Yes” and “No,” modifying these values can have unintended consequences.

	It is preferable to add new values to enumeration lists and deactivate unnecessary fields than to modify the text of the value.

Create New Data Fields

Information managers can create CDFs for those data fields 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.

When determining new data fields to add to IMSMA^NG, 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 field is critical to preserving the ability to search, calculate, sort and report information easily. The table below identifies the data types available in IMSMA^NG.

Data Type	Uses	Search
Date/Time	Storage of dates, times or dates and times. Examples include Date of Accident and Data Entry Date.	Is between, Is in the last
Country Structure	Storage of country structure information.	Is In, Is Not
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 Contamination Type and Drainage Features. Selection is displayed as checkboxes.	Is In, Is Not
Number	Storage of all numeric data used for calculations. Examples include Number of Teams and Total Audience Number.	Equals, Not Equal, Is Greater Than/Is Less Than, Is Null, Is Not Null, Is Between
Organisation	Storage of organisation information.	Is, Is Not, Parent Is
Place	Storage of place information.	Is, Is Not
Single 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 Temperature. Selection is displayed as radio buttons.	Is In, Is Not
Text	Storage of unstructured, textual data. Text data can be as small as a few characters or as long as several paragraphs. Text fields are good for storing data that cannot be stored in other formats, such as comments or narrative descriptions.	Is, Is Not, Contains, Does Not Contain

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.

	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.

IMSMA Enums (Multiple Select and Single Select)

Creating enumeration 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 fields for each IMSMA^NG item that are searchable, translatable and customisable. Enumeration 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 enumeration lists can be modified to reflect changing needs over time.

Enumeration list data can be used in tools such as the Impact Scoring tool as well as in sorting and filtering. Data in single-select enumeration 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 fields such as status, priority and type.

Creating a new enumeration list in IMSMA^NG requires information managers to first determine whether the enumeration 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 enumeration list can be added and the enumeration 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 fields are added to the Data Inventory Manager, information managers can proceed to form design to add the field to the data collection forms.

	When creating single-select enumeration lists, information managers should include a “Not specified” value, which users can select when a more appropriate value is not listed. This value helps prevent inaccurate data from being added to the database. Single-select enumeration lists cannot be changed to multiple select enumeration lists.

Using IMSMA^NG in a different language than English

IMSMA^NG 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 GUI i.e. what the user see and the data. How to translate the GUI is described here and how to translate the enumeration values and/or CDFs is described 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 both languages.

Buttons in the Data Inventory Manager Window
Button	Description
	If a data item is selected in the tree structure, a data category is added to the selected item. (left) If a category is selected, adds a CDF field to the selected category. (right)
	Allows you to translate the name of the categories. (left)
	If a data category is selected, allows you to change the data category name. (left) If a field with customisable values is selected, allows you to add or inactive enumeration values. (right) If a CDF is selected, allows you to change the label, description, active checkbox, or text display. If the CDF is a multiple selection or single selection type, allows you to also change the selection values. (right)
	If a data category is selected, allows you to remove a data category. (left) If a CDF is selected, allows you to remove unused CDFs. (right)
	Allows you to move the selected field(s) into a new or an existing data category. (right)