Difference between revisions of "Add values to enumeration list"
From IMSMA Wiki
m (Alnaucler moved page Add a Custom Option to Add values to enumeration list without leaving a redirect) |
|||
(10 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | {{ | + | {{Warning | Several of the enumeration lists are used by more than one field. Adding a value to an enumeration list will affect '''ALL''' fields that use that same enumeration list. |
− | }} | + | The enumeration list/category ''Yes No Answer'' are used by 86 fields. 42 of the 186 enumeration lists/categories are used by more than one field. }} |
− | + | <center> | |
+ | {| class="wikitable" | ||
+ | |- | ||
+ | | [[Image:CustomOptionsList warning1.png|400px]] | ||
+ | | width="10pt" | | ||
+ | | [[Image:CustomOptionsList warning2.png|400px]] | ||
+ | |- | ||
+ | | The values ''Ferrimagnetic'' and ''Titanomagnetites'' are added. | ||
+ | | | ||
+ | | The other fields that uses the same enumeration list are also affected. | ||
+ | |} | ||
+ | </center> | ||
+ | |||
+ | Before adding values to enumeration lists: | ||
+ | # consult the '''[[Data Dictionary]]''' | ||
+ | # look up which enumeration list/category is used | ||
+ | # consult the page [[Enumeration categories]] and verify that the category that you are about to update is not listed. | ||
+ | # is it possible to edit slightly the translation of an existing enumeration value instead of adding a value? | ||
+ | |||
+ | As an example the field ''Type of Infrastructure Blocked'' which used the enumeration list/category ''InfrastructureBlock'' will be used. | ||
<ol> | <ol> | ||
− | <li> | + | <li>In the '''Customisation''' menu → '''Data Inventory Manager'''.</li> |
− | + | [[Image:DIM enum.png|600px|center]] | |
− | <li> | + | <li>In the left pane of the Data Inventory Manager window, expand the item and data category where the the field is which uses the enumeration list.</li> |
− | <li> | + | <li>In the right pane, click the row associated with the field that you would like to add a enumeration value to. |
− | <li>Click the [[Image:FieldViewIcon.png]] button. | + | : Only system fields of types Multiple Select or Single Select use enumeration lists.</li> |
− | + | <li>Click the [[Image:FieldViewIcon.png]] button. </li> | |
[[Image:CustomOptionsList.png|center|400px|''Custom Options List Window'']] | [[Image:CustomOptionsList.png|center|400px|''Custom Options List Window'']] | ||
<div align="center"> | <div align="center"> | ||
''Custom Options List Window'' | ''Custom Options List Window'' | ||
− | </div></li> | + | </div> |
− | <li> | + | <li>As an example: it has been decided that ''Medical Facility'' is not detailed enough. ''Health Care Center'' and ''Hospital'' should be used instead.</li> |
− | + | <li>In the Custom Options List window, click the [[Image:FieldTemplateIcon.png]] button.</li> | |
[[Image:UserManual_OptionsEditor.png|center|400px|''Options Editor'']] | [[Image:UserManual_OptionsEditor.png|center|400px|''Options Editor'']] | ||
<div align="center"> | <div align="center"> | ||
''Options Editor'' | ''Options Editor'' | ||
− | </div | + | </div> |
− | <li>Enter the option in the '''Option''' field. The value can be | + | <li>Enter the option in the '''Option''' field. The value can be maximum 50 characters and can contain letters and numbers. Other characters should be avoided.</li> |
− | <li> | + | <li>Click the '''Save''' button.</li> |
− | + | <li>Repeat until all values are added.</li> | |
− | + | <li>In this example the next step is to '''[[Inactivate values in enumeration lists | inactivate]]''' the value ''Medical facility''.</li> | |
− | |||
− | |||
− | |||
</ol> | </ol> | ||
− | + | {{Note|Adding a value to an enumeration list will not automatically update existing Data Entry Form Templates that use the enumeration list. | |
+ | If the enumeration list/category that you would like to add a value to are used by more than one field and the value(s) you would like to add is '''not''' suitable for all affected fields <br/> | ||
+ | then it is recommended to use a '''[[Add Custom Defined Fields | CDF]]''' instead.}} | ||
{{NavBox HowTo Data Elements}} | {{NavBox HowTo Data Elements}} | ||
[[Category:NAA]] | [[Category:NAA]] |
Latest revision as of 19:16, 17 June 2017
The values Ferrimagnetic and Titanomagnetites are added. | The other fields that uses the same enumeration list are also affected. |
Before adding values to enumeration lists:
- consult the Data Dictionary
- look up which enumeration list/category is used
- consult the page Enumeration categories and verify that the category that you are about to update is not listed.
- is it possible to edit slightly the translation of an existing enumeration value instead of adding a value?
As an example the field Type of Infrastructure Blocked which used the enumeration list/category InfrastructureBlock will be used.
- In the Customisation menu → Data Inventory Manager.
- In the left pane of the Data Inventory Manager window, expand the item and data category where the the field is which uses the enumeration list.
- In the right pane, click the row associated with the field that you would like to add a enumeration value to.
- Only system fields of types Multiple Select or Single Select use enumeration lists.
- Click the button.
- As an example: it has been decided that Medical Facility is not detailed enough. Health Care Center and Hospital should be used instead.
- In the Custom Options List window, click the button.
- Enter the option in the Option field. The value can be maximum 50 characters and can contain letters and numbers. Other characters should be avoided.
- Click the Save button.
- Repeat until all values are added.
- In this example the next step is to inactivate the value Medical facility.
Custom Options List Window
Options Editor
Adding a value to an enumeration list will not automatically update existing Data Entry Form Templates that use the enumeration list.
If the enumeration list/category that you would like to add a value to are used by more than one field and the value(s) you would like to add is not suitable for all affected fields |
|