-
Adherence
A request through which the user asks for access to the data of a set of datasets via a DSA.
-
Alert
A notification that requires interaction from the recipient user.
-
Administration alert
A notification that communicates an incident in Anjana's automations with data systems that needs to be resolved to keep information consistent.
-
Audit
A set of actions that occur in external systems (structure alterations, ungoverned accesses…).
-
Contract
An agreement, generally written, by which two or more parties mutually commit to respecting and fulfilling a series of conditions. It is hosted in DSAs.
-
Dataset
Any set of data stored in an environment. It can be a Hive table, an HDFS file, a relational database table, etc.
-
Dataset Field
A field that makes up the schema of a structured dataset.
-
DSA (Data Sharing Agreement)
A contract that specifies the conditions under which data from a dataset can be accessed. It is what links a user to one or more datasets.
-
Validation Flows
They represent the authorization sequence that every 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 within an organization in order to create maximum possible value through the generation of knowledge based on information.
-
History
A set of actions that take place within Anjana, such as editing an object, launching a workflow, etc.
-
Process instance
An execution scenario of a process with its own parameterization.
-
LDAP (Lightweight Directory Access Protocol)
(In Spanish: Protocolo Ligero/Simplificado de Acceso a Directorios)
An 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 data.
In Anjana, lineage is the graphical representation of the relationships between different objects.
-
Metadata
Data that describes data structures, their content or format, which are fundamental for providing context about what the data represents, where it originates, how it moves through systems, who has access, or what it means for data to be of quality.
Metadata is classified into:
-
Business metadata: focused on data content and governance. Some examples include: definitions and descriptions of fields or tables, or for example, business rules, transformations, 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 data processing and access. For example: job execution logs, execution anomalies, error records…
-
Automatic Metadata
Automated extraction of metadata from source systems that allows knowledge of their structure or characteristics.
-
Template
A set of attributes (metadata) defined for a specific type of object.
-
Process
Any engine or software component registered in Anjana that, for each of the configurations it can have for its execution, has a process instance.
-
Role
A segmentation of users that grants them functionalities and execution capabilities in Anjana.
-
Snapshot
Metadata of an object and its relationships at a specific point in time, associated with each action performed from the application on the object.
-
Solution
A logical grouping of process instances that enables end-to-end knowledge of an application.
-
Business Unit, Container, or Organizational Unit
An area, business unit, or data domain in which Anjana's structures are organized. This can have a hierarchical structure.
-
Validation
Approval or rejection of a workflow.
-
Workflow
A sequence of steps that must be taken for the action requested by the user to be approved and executed.