Changes

|}

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.

{{HowTo's

</center>

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}}

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.

}}

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|It is preferable to add new values to pick lists and deactivate unnecessary elements than to modify the text of the value}}

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