Difference between revisions of "Data Inventory Manager"

Revision as of 12:01, 29 November 2012

The next step in setting up 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 IMSMANG. This step must be completed prior to designing forms for data entry so that these changes are reflected on the data entry forms. IMSMANG does not automatically change data entry forms when data elements are changed.

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

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 Data Inventory Manager window lists all IMSMA item attributes and allows you to group the item attributes into meaningful categories. The Data Inventory Manager window also allows you to manage custom defined fields (CDFs) and custom options.

The Data Inventory Manager window has two panes. The pane on the left displays a list of all items and the item attributes within them. The pane on the right displays the item attributes in the selected item or data category on the left.

Figure 140. Data Inventory Manager Window

Table 45. Icons in the Data Inventory Manager

Table 45. Icons in the Data Inventory Manager Window

Create New Data Elements

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.

When determining new data elements 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 is critical to preserving the ability to search, calculate, sort and report information easily. The table below identifies the data types available in IMSMANG and some search options for each.

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.

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.

* 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.

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.

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.

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 selected