Changes

Data Inventory Manager

6,993 bytes removed, 22:38, 17 June 2017

no edit summary

{{TOC right}}

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

Using the The objective of this step is to ensure that all data fields and values necessary for Mine action programme operation are available in {{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 This step should be completed prior to review designing Data Entry Form templates so that these elements to determine if these adequately address the data entry needs of the programme. Where there changes are elements that 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 Data Inventory Manager window lists all {{IMSMANG}} 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 data categories. The pane on the right displays the item attributes in the selected item or data category on the left. These data categories will also display in the [[Access the Data Entry Form Template Designer Window|Data Entry Form Template Designer window]]. [[Image:UserManual_DataInventoryManagerWindow.png|center|440px600px|''Data Inventory Manager Window'']]

<div align="center">

''Data Inventory Manager Window''

</div>

{| class="wikitable"=Data categories==__NOEDITSECTION__! colspan="2" | Icons {{IMSMANG}} comes with more than 1,000 system fields from installation and therefore it is important to search in the Data Inventory Manager Window before adding CDFs in order to [[Filter Item Attributes |-! Icon! Descriptiondetermine if a data field already exists]] '''before''' adding it as a CDF. The Data Inventory Manager shows the data field by item and [[Data Categories |sub-categories]] so information managers can quickly navigate and find the data fields. It is also possible to [[Add a Data Category | add more categories]] and [[Image:FieldTemplateIcon.pngAdd a Data Category | move fields between categories]]. {{Note | If an item there are many fields/CDFs in one category the Data Inventory Manager may be slow to load. If that is selected, adds the case then [[Move Fields Between Data Categories | move]] fields/CDFs into a custom defined field to the selected itemnew or existing category.}}

If a data category is selected, adds a data category to the selected category.==Modify Existing Fields==__NOEDITSECTION__|-{{HowTo's| [[Image:UserManual_TranslateSelectedTermsIcon.pngAdd values to enumeration list]]| Allows you to translate the selected terms. [[Change Display Option for Single Select]]|-[[Translate enumeration lists]]| [[Image:FieldViewIcon.pngAdd a Poly Property|Add a Poly Property]]| If a data category is selected}}Using the Data Inventory Manager, allows you information managers can customise the values of existing enumeration lists to reflect local programme needs. Information managers can add new values to change the data category nameenumeration lists and deactivate existing values.

If an item attribute with customisable [[Image:AdminGuide_ModifyingDataElements.png|center|500px|''Modifying Data Fields'']]<div align="center">''Modifying Data Fields''</div> For example, the existing “Safety and Security Threat” data field for Land includes the values is selectedthat are listed on the left side of the image. However, allows you to information managers can deactivate the values that their Mine action programmes don’t use and add or remove custom option the valuesthat they do, as shown on the right side of the image.

If a custom defined field While adding and deactivating new values is selectedan effective and important capability within {{IMSMANG}}, allows you to change information managers should approach changing the label, description, active checkbox, or text displayof existing values carefully. If the CDF is a multiple selection or single selection type, allows you to also change the selection Because many values. |-| [[Image:EcksButton.png]]| If a are used across different data category is selectedfields, allows you to remove a data category. If a CDF is selectedfor example, allows you to remove the CDFvalues “Yes” and “No,” modifying these values can have unintended consequences.|-| [[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| Allows you to move the selected item attribute into a new or an existing data category. |}

==Create New Data ElementsFields==__NOEDITSECTION__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.

{{HowTo's

|[[Data Categories|Data Categories]]

|[[Custom Defined Fields]]

|[[Add Custom Defined Fields]]

|[[View and/or Change Custom Defined Fields]]

|[[Add Subobject Custom Defined Fields|Add Subobject Custom Defined Fields]]

|[[Add a Custom Option|Add 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 {{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. The table below identifies the data types available ==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 GUI i.e. what the user see and the data. How to translate the GUI is described '''[[Update the Localisation Files | here]]''' and how to translate the enumeration values and/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>

{| class="wikitable"

! Left side

! Description

|-

! Data&nbsp;Type !! Uses !! Search Options| [[Image:UserManual_TranslateSelectedTermsIcon.png]]| Allows you to translate the name of the categories.

|-

| '''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, Is in a data category is added to the lastselected item.

|-

| '''Country Structure''' || Storage of country structure information[[Image:FieldViewIcon. png]]|| Is InIf a data category is selected, Is Notallows you to change the data category name.

|-

| '''Multiple Select''' [[Image:EcksButton.png]]|| Storage of structured If a data where values must be confined category is selected, allows you to certain pre-defined choices. Ideal for structuring delete a data for searching, reporting and translating. Examples include Contamination Type and Drainage Features. Selection is displayed as checkboxescategory. || 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! Right side! Description

|-

| '''Organisation''' |[[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| Storage of organisation informationAllows you to move the selected field(s) into a new or an existing data category. || Is, Is Not, Parent Is

|-

| '''Place''' [[Image:FieldViewIcon.png]]|| Storage of place informationIf a multi- or single select system field is selected, allows you to add or inactive enumeration values. If a CDF is selected, allows you to change the label, description and display format. || IsIf the CDF is a multiple selection or single selection type, Is Notallows you to also change the selection values.

|-

| '''Single Select''' [[Image:FieldTemplateIcon.png]]|| Storage of structured data where values must be confined If a category is selected, adds a CDF field 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 buttonsthe selected category. || Is In, Is Not

|-

| '''Text''' [[Image:EcksButton.png]]|| Storage of unstructured, textual data. Text data can be as small as If a few characters or as long as several paragraphs. Text elements are good for storing data that cannot be stored in other formatsCDF is selected, such as comments or narrative descriptionsallows you to delete unused CDFs. || Is, Is Not, Contains, Does Not Contain

|}

</center>

 

===Dates, Text and Numbers===__NOEDITSECTION__

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.

 

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

 

===IMSMA Enums (Multiple Select and Single Select)===__NOEDITSECTION__

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.

 

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

 

==Modify Existing Elements==__NOEDITSECTION__

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

 

[[Image:AdminGuide_ModifyingDataElements.png|center|500px|''Modifying Data Elements'']]

<div align="center">

''Modifying Data Elements''

</div>

 

This lets information managers track the individual types of land they defined. 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.

 

{{note|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==__NOEDITSECTION__

===Data Elements Groups===__NOEDITSECTION__

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 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 {{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===__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. 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.

{{note|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.}}

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

• ← Older edit

Alnaucler

NoPublic, bureaucrat, administrator

6,632

edits