Changes

The next step in setting up IMSMA^NG {{IMSMANG}} is to customise the data elements that are tracked. Using the information about additional data fields documented in Chapter 1, information managers can begin modifying existing data fields and creating CDFs. The objective of this step is to ensure that all data elements necessary for programme operations are available in IMSMA^NG{{IMSMANG}}. This step must be completed prior to designing forms for data entry so that these changes are reflected on the data entry forms. IMSMA^NG {{IMSMANG}} does not automatically change data entry forms when data elements are changed.

Using the IMSMA^NG {{IMSMANG}} 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 {{IMSMANG}} comes with more than 1,000 data elements in its initial configuration, it is important to review these elements to determine if these adequately address the data entry needs of the programme. Where there are elements that are not included in the initial configurations, information managers can use the Data Inventory Manager to create them.

Information managers can create CDFs for those data elements not predefined in IMSMA^NG{{IMSMANG}}. IMSMA^NG {{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.

When determining new data elements 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 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 {{IMSMANG}} and some search options for each.

To create date, text and number fields in IMSMA^NG{{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.

Creating pick lists is one of the most powerful functionalities available in the IMSMA^NG {{IMSMANG}} Data Inventory Manager. Using this functionality, information managers can create rich data attributes for each IMSMA^NG {{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.

Creating a new pick list in IMSMA^NG {{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 IMSMA^NG {{IMSMANG}} in other languages.

IMSMA^NG {{IMSMANG}} 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{{IMSMANG}}. 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 {{IMSMANG}} comes with a default local ID generator 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 generator per item subcategory. For example, create a local ID generator for completion reports, another for clearance reports and another for minefields. Also, establishing a convention for the local ID generators makes it easy to understand and find data.

| '''System Name''' || A value specified in the Client Configuration Tool of the IMSMA^NG {{IMSMANG}} TrayLauncher where system administrators can set a separate system name for each installation of IMSMA^NG{{IMSMANG}}. For example, the Headquarters installation could have “HQ” as a system name while a regional installation could have “R1.”

This lets information managers track the individual types of lands 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 IMSMA^NG {{IMSMANG}} and how they are tracked.

While adding and deactivating new values is an effective and important capability within IMSMA^NG{{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.

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. IMSMA^NG {{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 Data Entry Form template design.

For example, an information manager can create a group of land data elements called “Used” that contains all data elements used in the local version of IMSMA^NG {{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.

IMSMA^NG {{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 IMSMA^NG {{IMSMANG}} and the CDFs they create or modify. IMSMA^NG {{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 IMSMA^NG {{IMSMANG}} system and they can be exported using standard IMSMA^NG {{IMSMANG}} export functionality.

{{note|When running IMSMA^NG {{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 selected}}