In Anjana Data, selection-type attributes (for example: dropdown lists, combos or taxonomies) require additional configuration to define the possible values the user can choose.
These attributes are those whose Type corresponds to:
-
SELECT
-
SELECT_IMG
-
SELECT_IMG_TXT
-
TREE_SELECT
-
MULTI_SELECT
-
MULTI_SELECT_IMG
-
MULTI_SELECT_IMG_TXT
-
TREE_MULTISELECT
Attribute Definition Values Table in the Configuration Panel (Administrator view)
The configuration of these reference values is performed in the Attribute Definition Values table, where the reference metadata that will appear as selectable options in the Data Portal is stored.
Structure of the Attribute Definition Values table
Each value registered in this table is characterized by the following fields:
-
Id: unique identifier of the value.-
Automatically assigned from the Configuration Panel, based on database sequences.
-
-
value: attribute value that will be displayed in the selection list.-
When internationalization is configured, the
valueitself must be used as the translation key in thetranslationstable, generating one record for each configured language. -
For attributes of type SELECT_IMG, SELECT_IMG_TXT, MULTI_SELECT_IMG or MULTI_SELECT_IMG_TXT, the icon to be used must be stored in Minio or S3, with a name formed by concatenation:
<name del attribute_definition>_<value>.svg(example:
nivelGobierno_Gold.svg).
Example of naming convention for icons corresponding to image-type attributes
-
-
attributeDefinition: reference to the metadata attribute to which the values belong (references the attributes defined inAttribute Definitions).
Adding a new value for an attribute in the Attribute Definition Values table
Adding a new value involves adding a record to the Attribute Definition Values table for an attribute previously defined in Attribute Definitions.
To add a new value:
-
Click the New button in the top-right corner. This will open a wizard with the fields defined in the Table Structure section.
-
Fill in the fields according to the structure described:
-
value: with the value or its translation key (example:Unacceptable - Prohibited AI System). -
attributeDefinition: select the attribute to which the value belongs (example:10321-nivelRiesgo-SELECT).
-
-
Click Save to save or Cancel to discard.
Note: After adding values, it is necessary to run the Clear cache action from the Configuration Panel (Actions > Clear cache) for the changes to be applied and become visible in the Data Portal.
Modifying a value of an attribute in the Attribute Definition Values table
Modifying an existing value must be done with caution, as it can impact both the information displayed in the Data Portal and the consistency of the configured metadata.
The fields in this table are sensitive and require that changes be applied following a proper order:
Case 1: No governed assets exist in the Data Portal:
-
Modifying the
valuefield requires executing the following steps in order:-
Modify the text directly or, if internationalized, also update the records in the
Translationstable. In this case, decide whether it is sufficient to change only the translation value (value) or whether it is also necessary to adjust the key (config_key). -
Review and, if necessary, modify the existing configurations in the
Edition Configurationtable. -
If the attribute is of type SELECT_IMG, SELECT_IMG_TXT, MULTI_SELECT_IMG or MULTI_SELECT_IMG_TXT, and the
valuechange implies a new icon, it will be necessary to upload the corresponding file to Minio or S3 following the established naming convention:<name del attribute_definition><value>.svg
-
-
Modifying the
attributeDefinitionfield can be done if there are no governed assets.
If governed assets exist in the Data Portal:
-
Modifying the
valuefield requires executing the following steps in order:-
Modify the text directly or, if internationalized, also update the records in the
Translationstable. In this case, decide whether it is sufficient to change only the translation value (value) or whether it is also necessary to adjust the key (config_key). -
Review and, if necessary, modify the existing configurations in the
Edition Configurationtable. -
Run a Mass attribute edit from the Data Portal to force the update of values across all affected templates.
-
If the attribute is of type SELECT_IMG, SELECT_IMG_TXT, MULTI_SELECT_IMG or MULTI_SELECT_IMG_TXT, and the
valuechange implies a new icon, it will be necessary to upload the corresponding file to Minio or S3 following the established naming convention:<name del attribute_definition><value>.svg
-
-
Modifying the
attributeDefinitionfield cannot be done when governed assets already exist.
Note: After the modification, it is necessary to run the Clear cache action from the Configuration Panel (Actions > Clear cache) for the changes to be applied and become visible in the Data Portal.
Configuring reference values via direct database access (Developer view)
The table that stores the values of selection attributes is anjana.attribute_definition_value.
|
Column |
Type |
Constraints / Notes |
|---|---|---|
|
|
|
PRIMARY KEY. Value identifier. Managed by sequences. |
|
|
|
FK → |
|
|
|
Display value text / translation key. Not null. |
Below is an example script to configure reference values for a SELECT type attribute to set the risk level of an AI system:
INSERT INTO anjana.attribute_definition_value
(id_attribute_definition_value, id_attribute_definition, value)
VALUES
(2124, 10321, 'Inaceptable - Sistema de IA prohibido'),
(2125, 10321, 'Alto - Sistema de IA de alto riesgo'),
(2126, 10321, 'Limitado - Sistema de IA con obligaciones de transparencia'),
(2127, 10321, 'Mínimo - Sistemas de IA de riesgo mínimo');
Important:
-
Once the insert has been executed, run the sequence update for the table. (From the Configuration Panel at
Actions > Reset DQ sequencesyou can update the sequences for all tables, including this one). -
The entire responsibility for the configuration logic falls on the developer executing SQL queries directly against the tables. It is strongly recommended to carefully review the Structure section.