Changes

Jump to: navigation, search

Data Inventory Manager

1,934 bytes removed, 15:01, 11 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 database in two ways:* modifying existing data fields, information managers can begin modifying existing i.e. data fields and that exist in the database from installation which often are referred to as system fields* creating new custom defined data fields which are referred to as Custom Defined Fields (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.
{{note|The objective of this step is to ensure that all data fields and options necessary for programme operations are available in {{IMSMANG}} does not automatically change . This step should be completed prior to designing forms for data entry forms when data elements so that these changes are changedreflected on the Data Entry Forms.}}
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 note|{{IMSMANG}} comes with more than 1,000 predefined 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 does '''not''' automatically change Data Entry Forms when changes are elements that are not included made in the initial configurations, information managers can use the Data Inventory Manager to create them. }}
The {{IMSMANG}} comes with more than 1,000 system fields from installation and therefore it is important to search in the Data Inventory Manager categorises all data elements by the type of item they belong before adding CDFs in order to so that information managers can quickly navigate to the desired determine if a data elementsfield already exists '''before''' adding it as a CDF.
The Data Inventory Manager window lists all {{IMSMANG}} shows the data field by item attributes and allows you to group [[Data Categories | sub-categories]] so information managers can quickly navigate and find the item attributes into meaningful categoriesdata fields. The Data Inventory Manager window It is also allows you possible to manage CDFs [[Add a Data Category | add more categories]] and custom options[[Add a Data Category | move fields between categories]].
[[Image:UserManual_DataInventoryManagerWindow.png|center|440px|''Data Inventory Manager Window'']]
</div>
{{Note | class="wikitable"! colspan="2" | Buttons If there are many item attributes/CDFs in one category the Data Inventory Manager Window |-! Button! Description|-| may be slow to load. If that is the case then [[Image:FieldTemplateIcon.pngMove Item Attributes into a Data Category | move]]item attributes/CDFs into a new or existing category.}} | ==Modify Existing Elements==__NOEDITSECTION__* If a In addition to creating new data item is selected in elements using the tree structureData Inventory Manager, a 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 category is 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 the selected itemnew forms. (left)* If {{note|Deactivating or changing a category is selected, adds a custom defined field value in the Data Inventory Manager does not change the forms that use the original value. Additional steps should be taken to prevent the selected categoryoriginal value from being used for data entry. These include updating and republishing all data entry forms that use the deactivated or changed value. (right)}}|-| [[Image:UserManual_TranslateSelectedTermsIconFor 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.png]]| Allows you to translate However, information managers can deactivate the values that their programmes don’t use and add the values that they do, as shown on the name right side of the categoriesfigure. (left)|-| [[Image:FieldViewIconAdminGuide_ModifyingDataElements.png|center|500px|''Modifying Data Elements'']]| <div align="center">''Modifying Data Elements''</div>  * If a data category is selectedThis lets information managers track the individual types of land they defined. Likewise, allows you the ability to change modify existing data elements gives information managers fine control over all the data category nameelements they want to track in {{IMSMANG}} and how they are tracked. (left)
* If While adding and deactivating new values is an item attribute with customisable effective and important capability within {{IMSMANG}}, information managers should approach changing the text of existing values is selectedcarefully. Because many values are used across different data elements, for example, the values “Yes” and “No, allows you to add or inactive option ” modifying these valuescan have unintended consequences. (right)
* If a custom defined field {{note|It is selected, allows you preferable 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 add new values. (right)|-| [[Image:EcksButton.png]]| * If a data category is selected, allows you to remove a data category. (left)* If a CDF is selected, allows you pick lists and deactivate unnecessary elements than to remove unused CDFs. (right)|-| [[Image:UserManual_MoveSelectedItemAttributeIcon.png]]| Allows you to move modify the text of the selected item attribute into a new or an existing data categoryvalue. (right) |}}
{{Note | If there are many item attributes/CDFs in one category the Data Inventory Manager may be slow to load. If that is the case then [[Move Item Attributes into a Data Category | move]] item attributes/CDFs into a new or existing category.}}
==Create New Data Elements==__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.
* Single-select pick lists cannot be changed to multiple select pick lists.}}
==Modify Existing ElementsUsing {{IMSMANG}} in a different language than English==__NOEDITSECTION__In addition {{IMSMANG}} provides the capability to creating new data elements using translate and run the entire system in different languages. To fully translate the Data Inventory Managersystem into one or more languages, information managers can customise there are two parts to consider. The GUI i.e. what the user see and the values of existing pick lists to reflect local programme needsdata. Information managers can add new values How to translate the GUI is described '''[[Update the pick lists Localisation Files | here]]''' and deactivate existing values. Deactivating existing values does not remove how to translate the enumeration values from and/or CDFs is described '''[[Export the database nor does it change existing data or formsTranslations | here]]'''. Rather, it removes If the options from 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 Source Tree Data Entry Form may contain labels in the Form Designer so that the values can no longer be added to new formsboth languages.
{{note|Deactivating or changing a value class="wikitable"! colspan="2" | Buttons in the Data Inventory Manager does not change Window |-! Button! Description|-| [[Image:FieldTemplateIcon.png]]| * If a data item is selected in the forms that use tree structure, a data category is added to the original valueselected item. Additional steps should be taken (left)* If a category is selected, adds a custom defined field to prevent the original value from being used for data entryselected category. (right)|-| [[Image:UserManual_TranslateSelectedTermsIcon.png]]| Allows you to translate the name of the categories. (left)|-| [[Image:FieldViewIcon. These include updating and republishing all png]]| * If a data entry forms that use category is selected, allows you to change the deactivated or changed valuedata category name.}}(left)
For example, * If an existing “Safety and Security Threat” data element for land could include the item attribute with customisable values that are listed on the left side of the figure below. Howeveris selected, information managers can deactivate the values that their programmes don’t use and allows you to add the or inactive option 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 * If a custom defined. Likewisefield is selected, the ability allows you to modify existing data elements gives information managers fine control over all change 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}}label, description, active checkbox, information managers should approach changing the or text of existing values carefullydisplay. Because many values are used across different data elements, for exampleIf the CDF is a multiple selection or single selection type, allows you to also change the selection values “Yes” and “No,” modifying these values can have unintended consequences.(right)|-{{note|It is preferable to add new values to pick lists and deactivate unnecessary elements than to modify the text of the value[[Image:EcksButton.}}png]]| ==Manage Data Elements==__NOEDITSECTION__===Data Elements Groups===__NOEDITSECTION__All data elements in the Data Inventory Manager are grouped by item. When * If a data element category is added to an itemselected, it becomes an attribute of that item and cannot be moved allows you 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 remove a data elements, making it easier to find them during Data Entry Form template designcategory. (left) For example, an information manager can create * If 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 CDF 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 waysselected, users browsing the Data Inventory Manager or designing data entry forms can quickly navigate allows you to the elements they needremove unused CDFs.(right)|-===Data Elements Translation===__NOEDITSECTION__| [[Image:UserManual_MoveSelectedItemAttributeIcon.png]]{{IMSMANG}} provides the capability | Allows you to translate and run move the entire system in different languages. To fully translate the system selected item attribute into one a new or more languages, there are two parts to consider. Information managers can translate the predefined an existing data elements that come with {{IMSMANG}} and the CDFs they create or modifycategory. {{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(right) |}} 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 IMSMA NG Administration}}
[[Category:NAA]]
Alnaucler
NoPublic, bureaucrat, administrator
6,632
edits
Retrieved from "http://mwiki.gichd.org:8090/IM/Special:MobileDiff/23197"

Navigation menu