-
Adherence
Request through which the user asks for access to the data of a set of datasets by means of a DSA.
-
Alert
Notification that requires interaction from the receiving user.
-
Administration Alert
Notification that reports an incident in Anjana's automations with the data systems that needs to be fixed in order to keep the information consistent.
-
Audit
Set of actions that occur in external systems (alteration of structures, ungoverned access...).
-
Contract
Agreement, usually written, by which two or more parties mutually commit to respect and comply with a series of conditions. It is hosted in the DSAs.
-
Dataset
Any set of data stored in an environment. It can be a Hive table, an HDFS file, a table in a relational DB, etc.
-
Dataset Field
Field that makes up the schema of a structured dataset.
-
DSA (Data Sharing Agreement)
Contract that specifies the conditions under which the data of a dataset can be accessed. It is what links a user to a dataset (or more).
-
Validation Flows
They represent the authorization sequence that any action requested or performed by a user must go through.
-
Data Governance
Data governance is the management of the availability, quality, security, and use of data used in an organization in order to create the maximum possible value through the generation of knowledge based on information.
-
History
Set of actions that take place within Anjana; it can be an edit of an object, the launch of a workflow, etc.
-
Process Instance
An execution scenario of a process with its own parameterization.
-
LDAP (Lightweight Directory Access Protocol)
(In Spanish, Lightweight/Simplified Directory Access Protocol)
Application-level protocol that allows access to an ordered and distributed directory service to search for various information in a network environment.
-
Lineage
Data traceability that makes it possible to know the origin, movements, characteristics, and quality of the data.
In Anjana, lineage is the graphical representation of the relationships between the different objects.
-
Metadata
Data that describes data structures, their content, or their format, which are fundamental to providing context on what the data represents, where it originates, how it moves through the systems, who has access, or what it means for the data to be of quality.
Metadata is classified into:
-
Business metadata: focused on the content and governability of the data. Some examples are: definitions and descriptions of fields or tables, or, for example, business rules, transformation, or calculations
-
Technical metadata: those that provide information about the technical details of the data, its storage, or processing. For example, column or table names, column properties, CRUD rules, etc
-
Operational metadata: those that describe details of the processing and access to the data. For example: execution job logs, anomalies in executions, error logs...
-
Automatic Metadata
Automated extraction of metadata from source systems that allows knowledge of their structure or characteristics.
-
Template
Set of attributes (metadata) defined for a specific type of object.
-
Process
Any engine or piece of software registered in Anjana that, for each of the configurations it can have for its execution, has a process instance.
-
Role
Segmentation of users that grants them functionalities and execution capabilities in Anjana.
-
Snapshot
Metadata of an object and its relationships at a given moment, which is associated with each action performed from the application on the object.
-
Solution
Logical grouping of process instances that allows end-to-end knowledge of an application.
-
Business Unit, Container, or Organizational Unit
Area, business unit, or data domain in which Anjana's structures are organized. It can have a hierarchical structure.
-
Validation
Approval or rejection of a workflow.
-
Workflow
Sequence of steps that must be taken for the action requested by the user to be approved and executed.