Template Sections

In Anjana Data, sections are second-level blocks within the dynamic forms of metadata templates. Their main purpose is to organize and classify the specific attributes of an object (entity or relationship) within a menu, allowing 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 form (example: DETAIL, DATA QUALITY, EXTENDED GOVERNANCE).

• Level 2 – Section: Subsections within each menu that group related attributes (example: within the DETAIL menu, sections such as FUNCTIONAL, GOVERNANCE, SECURITY AND DATA PROTECTION and TECHNICAL).

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, for structuring metadata templates.

Structure of the Sections table

Each section is characterized by the following fields:

• Id: unique identifier of the section.

  • Automatically assigned from the Configuration Panel.

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

  • When internationalization is configured, the name value itself should be used as a translation key in the translations table, creating one record per language.

• Description: description of the section. This description (or its translation value) is visible in the metadata template and helps understand the content of the section.

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

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

• Menu: menu to which the section belongs.

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

Adding a Section in the Menus table

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

To add the record and register 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., FUNCTIONAL).

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

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

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

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

Modifying a Section in the Sections table

Modifying 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 modification impacts the corresponding records in translations (same config_key as Name and Description). In this case, consider whether it is sufficient to modify only the translation value (value) or whether the key (config_key) also needs to be changed.

• Order: the modification only affects the repositioning of the section within the menu, without additional impact.

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

  • If no governed assets exist in the Data Portal, modification is possible but requires:

    • Previously deleting attribute validations (templateAttributeValidations).

    • Deleting versioning rules (Edition Configuration).

    • Deleting attribute relationships (Attribute Relationship).

  • If governed assets exist in the Data Portal, the modification cannot be performed.

Configuring sections via direct database access (Developer view)

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

Below is an example script to configure the FUNCTIONAL section of the DETAIL menu for DATASET:

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