Template Sections

In Anjana Data, sections are second-level blocks within the dynamic forms of metadata templates. Their main function is to organize and classify the specific attributes of an object (entity or relationship) within a menu, allowing the information to be structured in a clear and navigable way.

Each menu must contain at least one section, and each section can group multiple related metadata attributes.

In this way, menus and sections structure metadata into two hierarchical levels:

• Level 1 – Menu: Main categories that appear in the object's form (example: DETALLE, CALIDAD DE DATOS, GOBIERNO EXTENDIDO).

• Level 2 – Section: Subsections within each menu that group related attributes (example: within the DETALLE menu, sections such as FUNCIONAL, GOBIERNO, SEGURIDAD Y PROTECCIÓN DE DATOS and TÉCNICO).

Thanks to this hierarchical organization, users can easily navigate the Data Portal forms and maintain consistency in asset documentation.

Sections Table in the Configuration Panel (Administrator view)

Sections are configured in the Sections table of the Configuration Panel. Defining sections is the second step, after creating menus, to structure metadata templates.

Structure of the Sections table

Each section is characterized by the following fields:

• Id: unique identifier of the section.

  • Assigned automatically from the Configuration Panel.

• Name: visible name of the section within the menu.

  • If internationalization is configured, the value of name itself must be used as the translation key in the translations table, creating one record per language.

• Description: description of the section. This description (or its translated value) is visible in the metadata template and makes it easier to understand the section's content.

  • It can also be internationalized using the value of Description as config_key in translations.

• Order: display order of the section within the menu (1, 2, 3, …).

• Menu: menu the section belongs to.

  • Corresponds to a value from the Menus table, explicitly indicating the main block in which the section is grouped.

Creating a Section in the Menus table

Creating a new section involves adding a new record to the Sections table, always associated with a previously configured menu.

To add the record and create a new section:

1. Click the New button in the top right corner. This will open a wizard with the fields defined in the Structure of the Sections table section.

2. Fill in the fields according to the structure described:

   • Name: with the name or its translation key (e.g., FUNCIONAL).

   • Description: with the description or its translation key (e.g., FUNCIONAL INFORMATION OF DATASET).

   • Order: with the position the section will occupy within the menu (e.g., 1).

   • Menu: select the menu the section will belong to (e.g., 1-DETALLE-DATASET).

3. Click Save to save the section, or Cancel to discard it.

Editing a Section in the Sections table

Editing a record in the Sections table must be done with caution, as it can have different levels of impact depending on the field affected:

• Name and Description:

  • If internationalization has not been configured, the texts can be modified without impact.

  • If internationalization has been configured, the change impacts the corresponding records in translations (with the same config_key as Name and Description). In this case, assess whether it is enough to modify the translated value (value) or whether the key (config_key) also needs to change.

• Order: the change only affects the repositioning of the section within the menu, with no additional impact.

• Menu: the change can have a significant impact, since it involves moving all the associated configuration (attributes, validations, versioning rules, and attribute relationships) to another menu.

  • If there are no governed assets in the Data Portal, the change is possible but requires:

    • First removing attribute validations (templateAttributeValidations).

    • Removing versioning rules (Edition Configuration).

    • Removing relationships between attributes (Attribute Relationship).

  • If there are governed assets in the Data Portal, the change cannot be made.

Configuring sections via direct database access (Developer view)

The database (DB) table that contains the parameterization of the metadata template sections is anjana.sections and has the following structure.

Below is an example script to configure the FUNCIONAL section of the DETALLE menu for DATASET:

INSERT INTO anjana.sections
(id_section, description, id_menu, "name", order_section)
VALUES(1, 'FUNCIONAL INFORMATION OF DATASET', 1, 'FUNCIONAL', 1);