Menus
Menus are the highest-level configurable blocks in the template, and as many can be set up as needed. Within each one, different metadata sections can be defined.
The text to the right of the menu name is its description.
Menus can be collapsed or expanded in the object view.
Sections
Within each menu, different sections are configured that group and classify the metadata attributes in an orderly way. Sections are fully configurable and as many can be defined as the user needs.
The text to the right of the section name is its description.
Sections can also be collapsed or expanded in the object view.
Template navigation panel
From the navigation panel located on the left side of the form, you can navigate to the corresponding menu or section.
Attributes
Object attributes complete their metadata; they are data that characterize the data itself. These attributes are fully configurable for each Anjana Data object.
For each attribute, an informational message can be configured, which will be visible when hovering the mouse over the i icon.
The possible attribute types in Anjana are the following:
Short text
Allows inserting short plain text.
Example in the Anjana Portal:
Example for API:
Text array
Allows inserting one or several short plain text values.
Example in the Anjana Portal:
Example for API:
International short text
Allows inserting plain text for each application language by selecting the corresponding flag.
Example in the Anjana Portal:
Example for API:
Long text
Allows inserting extensive plain text: more than one line, paragraphs, etc.
Example in the Anjana Portal:
Example for API:
International long text
Allows inserting extensive text for the different application languages by selecting the corresponding flag.
Example in the Anjana Portal:
Example for API:
Rich text
Allows inserting extensive text with HTML markup.
The only HTML tags allowed are: <a>, <blockquote>, <br>, <em>, <h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <img>, <li>, <ol>, <p>, <pre>, <s>, <span>, <strong>, <sub>, <sup>, <u> and <ul>.
Example in the Anjana Portal:
Example for API:
International rich text
Allows inserting extensive text with HTML markup.
The only HTML tags allowed are: <a>, <blockquote>, <br>, <em>, <h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <img>, <li>, <ol>, <p>, <pre>, <s>, <span>, <strong>, <sub>, <sup>, <u> and <ul> for the different application languages, depending on which flag is clicked.
Example in the Anjana Portal:
Example for API:
Integer range
Allows selecting an integer within a range with a defined minimum and maximum.
Example in the Anjana Portal:
Example for API:
Integer
Allows inserting integer numbers.
Example in the Anjana Portal:
Example for API:
Integer array
Allows inserting one or several integer numbers.
Example in the Anjana Portal:
Example for API:
Decimal
Allows inserting decimal numbers. Numbers without decimals can be included if there is no validation preventing it.
Example in the Anjana Portal:
Example for API:
Decimal array
Allows inserting one or more decimal values. Numbers without decimals can be included if there is no validation preventing it.
Example in the Anjana Portal:
Example for API:
Boolean
Allows inserting a boolean: true (selected) and false (not selected).
Example in the Anjana Portal:
Example for API:
Boolean array
Allows inserting one or more boolean values.
Example in the Anjana Portal:
Example for API:
Date
Allows inserting a date, selecting it from a calendar.
In date-type fields, the format must be YYYY-MM-DDThh:mm:ssZ, for example: 2020-11-11T10:10:10Z.
The calendar and the selected date are formatted according to the user's language; however, its value follows the same format regardless of the language.
Example in the Anjana Portal:
Example for API:
Date array
Allows inserting one or more dates, selecting them from a calendar.
In date-type fields, the format must be YYYY-MM-DDThh:mm:ssZ, for example: 2020-11-11T10:10:10Z.
The calendar and the selected date are formatted according to the user's language; however, its value follows the same format regardless of the language.
Example in the Anjana Portal:
Example for API:
File
Allows inserting a file.
The file must be uploaded beforehand with an S3/Minio client (the portal itself allows uploading through this field or from the API), and its file name will be the corresponding ARI (internal file identifier in Anjana). This ARI is passed as the input value in the API call.
Example in the Anjana Portal:
Example for API:
NOTES:
-
The name of files attached to templates must not contain ‘:’, ‘#’, ‘(‘ or ‘)’ so as not to interfere with the application's internal logic.
-
The maximum file size allowed for upload is 10MB; this limit can be changed via configuration.
File array
Allows inserting one or more files.
The file must be uploaded beforehand with the S3/Minio client (the portal itself allows uploading through this field or from the API), and its file name will be the corresponding ARI (internal file identifier in Anjana). This ARI is passed as the input value in the API call.
Example in the Anjana Portal:
Example for API:
NOTES:
-
The name of files attached to templates must not contain ‘:’, ‘#’, ‘(‘ or ‘)’ so as not to interfere with the application's internal logic.
-
The maximum file size allowed for upload is 10MB; this limit can be changed via configuration.
URL
Allows including a URL and navigating to it by opening a new tab in the browser.
Example in the Anjana Portal:
Example for API:
URL array
Allows including one or several URLs and navigating to them by opening a new tab.
Example in the Anjana Portal:
Example for API:
User
Allows locating users by their name in the identity management systems configured in Anjana and selecting one.
Example in the Anjana Portal:
Example for API:
User array
Allows locating users by their name in the identity management systems configured in Anjana and selecting one or several.
Example in the Anjana Portal:
Example for API:
Entity
The ENTITY_SEARCH type attribute allows entering an entity as an attribute. It is used in relationships to identify the source entity and target entity, or in object templates where an entity needs to be referenced without creating a relationship between them.
The value must be the ARI of the chosen entity (internal object identifier in Anjana).
Examples in the Anjana Portal:
In this case, an entity can be located directly by searching for it by name:
If you want to locate an entity using other parameters, in the search box that opens when clicking the icon, you can search by name, ARI, or an attribute, or use the displayed filters.
Example for API:
Entity array
This attribute is used to enter one or more entities in a template so they can be referenced without creating a relationship between them.
The value must be the ARI of the chosen entity (internal object identifier in Anjana).
Searches on this attribute are similar to the Entity type attribute; that is, from the attribute itself only entities will be searched by name, and from the search box it will be possible to include other search parameters such as the ARI or any of the filters.
Example in the Anjana Portal:
Example for API:
Contained entities
This attribute allows selecting one or several entities, creating relationships between the object that contains it and each of the entities included in the field.
It can only be used as a contained-entities attribute in DSA, input and output datasets in instance, and related instances in solution.
The value must be the ARI of the chosen entity (internal object identifier in Anjana). Filtered searches are also allowed.
Example in the Anjana Portal:
Example for API:
Reference metadata
Allows selecting a value from a preconfigured list of Reference Metadata.
Example in the Anjana Portal:
Example for API:
Reference metadata array
Allows selecting one or more values from a preconfigured list of Reference Metadata.
Example in the Anjana Portal:
Example for API:
Organizational unit
Allows selecting an organizational unit from the list of all of them.
Example in the Anjana Portal:
Example for API:
Organizational Unit array
Allows selecting one or several organizational units from the list of all of them.
Example in the Anjana Portal:
Example for API:
Reference metadata with icon
Allows selecting an image from a preconfigured list.
Example in the Anjana Portal:
Example for API:
Reference metadata with icons array
Field that allows selecting one or several images from a preconfigured list.
Example in the Anjana Portal:
Example for API:
Reference metadata with icon and text
Allows selecting a value from a preconfigured list of Reference Metadata. Unlike the single-selection Reference Metadata field, this one includes an image associated with the value.
Example in the Anjana Portal:
Example for API:
Reference metadata with icons and text array
Allows selecting one or several options from a preconfigured list of Reference Metadata. Unlike the multiple-selection Reference Metadata field, this one includes an image associated with the value.
Example in the Anjana Portal:
Example for API:
Single-selection taxonomy
Allows selecting a node from a hierarchical tree, preconfigured as Reference Metadata.
Example in the Anjana Portal:
Example for API:
Multiple-selection taxonomy
Allows selecting one or several nodes from a hierarchical tree preconfigured as Reference Metadata.
Example in the Anjana Portal:
Example for API:
NOTES:
-
The “name” attribute of any entity or relationship registered in Anjana Data must not contain ‘:’ or ‘#’ so as not to interfere with the application's internal logic.
Custom attributes
In addition to the predefined attributes existing in a template, it is possible to add certain custom attributes for each object. These attributes in Anjana are the Custom Attributes.
To do this, Anjana adds to each object's template its own section called Custom Attributes, from which it is possible to create new attributes or reuse an attribute belonging to a template other than the object's own.
To create an attribute, it is necessary to indicate the label (name) of the attribute and its type, choosing one from among the existing ones. Additionally, its description can be added.
Once Confirmed, the attribute is added to the object and remains pending for the user to enter a value for it.
Not all attribute types can be created as custom attributes, since some require a predefined list of values (Reference Metadata or taxonomy type attributes); these are not allowed.
Additionally, attributes from other templates can be added to a different object that does not contain them. In this case, the user must type its name in the label (internal attribute name) so that Anjana suggests the existing attributes, automatically completing the rest of the fields.
Once the attribute has been added to the object, a value can be entered for it.
Template attributes of type entity_container (dsaContent, instanceInDataset, instanceOutDataset, solutionRelatedInstance), attributes used for versioning (datasetFields), or attributes used for Excel import (processAri, solutionAri) cannot be reused in other objects as custom attributes.
Additionally, it is not possible to add a custom attribute to an object whose name is the same as another attribute already existing in its template.
Language selector
Anjana is a multi-language application, and as such, any user can choose in their profile among any of the configured languages in order to view the tool in the chosen language. With this, the information shown in the Portal, the notifications, the object history, the comments in workflow validations… will appear in their language.
However, even though the language chosen in the profile is one specific language, it is possible to view an object's template or a particular attribute (of international text type) in a different language, so that the user can read the information entered in the different languages configured in Anjana.
