Changes

Data Inventory Manager

132 bytes added, 20:26, 10 February 2014
Version 6.0
|-
| [[Image:FieldTemplateIcon.png]]
| If an item is selected, adds a data category custom defined field to the selected item.
If a data category is selected, adds a custom defined field data category to the selected category.
|-
| [[Image:UserManual_TranslateSelectedTermsIcon.png]]
If an item attribute with customisable values is selected, allows you to add or remove custom option values.
If a custom defined field is selected, allows you to change the label , description, active checkbox, or descriptiontext display. If the CDF is a multiple selection or single selection type, allows you to also change the selection values.
|-
| [[Image:EcksButton.png]]
| Allows If a data category is selected, allows you to remove a data category. If a CDF is selected, allows you to remove the CDF.
|-
| [[Image:UserManual_MoveSelectedItemAttributeIcon.png]]
| '''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 Contamination Type and Drainage Features. Selection is displayed as checkboxes. || Is In, Is Not
|-
| '''Number''' || Storage of all numeric data used for calculations. Examples include Number of Ordnance Teams and Total PopulationAudience Number. || Equals, Not Equal, Is Greater Than/Is Less Than, Is Null, Is Not Null, Is Between
|-
| '''Organisation''' || Storage of organisation information. || Is, Is Not, Parent Is
| '''Place''' || Storage of place information. || Is, Is Not
|-
| '''Single 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 TerrainTemperature. Selection is displayed as radio buttons. || Is In, Is Not
|-
| '''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, Is Not, Contains, Does Not Contain
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__
{{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 “Mine Action Area Type” “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'']]
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__
{{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 IMSMA}}
518
edits