A
B
| Batch processing |
|---|
| The process of adding a crosswalk that holds cleansed attribute values. The cleansing can be profile-level or match-level. |
| Big Data |
|---|
| Inside Reltio we associate data with its source via the crosswalk which plays the role of a unique identifier. A Reltio entity can have multiple crosswalks. Each crosswalk has its own attributes such as source type, crosswalk value, source table, etc. |
C
| Cleanse |
|---|
| The process of adding a crosswalk that holds cleansed attribute values. The cleansing can be profile-level or match-level. |
| Crosswalk |
|---|
| Inside Reltio we associate data with its source via the crosswalk which plays the role of a unique identifier. A Reltio entity can have multiple crosswalks. Each crosswalk has its own attributes such as source type, crosswalk value, source table, etc. |
| Configuration |
|---|
| The configuration is responsible for modifying the behavior of your tenant. |
D
| Data quality (DQ) |
|---|
| Data quality is responsible for the accuracy, validity, completeness, consistency, and relevancy of the data and whether it is up-to-date. |
E
F
G
| Golden Record |
|---|
| This is the single source of truth that contains all the necessary and most accurate data for an object. |
H
I
| Interaction |
|---|
Represents an event that takes place at a specific time, like a sales transaction. |
J
K
L
| Layered Reltio data model |
|---|
| Reltio has a three-layer metadata configuration model. L1 – This is the default root layer that comes preconfigured and is controlled by Reltio’s Product Management. L2 – This is the layer that holds containers of industry-specific customizations and is again controlled by Reltio’s Product Management. L2 inherits L1. L3 – L3, also known as customer tenant, is the layer that is completely customizable by you. L3 inherits L2 and L1. |
M
| Master data and MDM |
|---|
| Master data is the essential core data that describes objects and entities within a business enterprise. Master data management (MDM) provides the tools for establishing a single master record across different data sources. |
| Matching |
|---|
| The process of determining if two entities are being semantically the same. |
| Merging |
|---|
| The process of consolidating two entities into one based on customized merge rules in the L3 configuration. The merge rules can be suspect, automatic, relevance-based, and custom. |
| Merge tree |
|---|
| A merge tree corresponds to a merge operation between two or more entities. |
N
O
| OV (operational value) |
|---|
| The value of the attribute that survives after the survivorship rules have been applied. It can accept true or false. |
P
| Progressive stitching |
|---|
| This is the process that spans stitching together information that is of a limited amount and comes from a limited number of data sources and building progressively on top of that information in order to create a full 360 profile. |
Q
R
| Real-time processing |
|---|
| Processing the information at the exact moment when it is obtained. |
| Reference data and RDM |
|---|
| Reference data is data that can be represented differently throughout the source systems and from a business point of view is data that rarely changes. Reference data is used for lookups/drop-downs in Reltio UI and it is controlled by the Reference Data Management (RDM) application and the RDM API. |
| Relationship |
|---|
| An object that serves as a connection between two entities. |
| Reltio |
|---|
| The Reltio Connected Data Platform is a cloud SaaS solution for creating and managing core data based on the foundational principles of Master Data Management (MDM). |
| Reltio Entity |
|---|
| A record that represents a real-world entity and holds attributes. The Reltio graph treats the entity as a single node. |
| Reltio Profile |
|---|
| An aggregation of entities, their relationships, and their interaction data. |
S
| Survivorship |
|---|
| The process of consolidating records to determine the operational value (OV) for an attribute. It happens on the fly and is based on customized survivorship rules in the L3 configuration. |
| System of record |
|---|
| This is the original source of data; System of entry |
| System of reference |
|---|
| This is the system where the most current and accurate data is held; we can say that it is a collection of golden records. |
T
| Tenant |
|---|
| Reltio provides data tenants where customers can manage their data. |
| Transaction |
|---|
| This is a logical unit of a set of tasks that are related to each other. For a transaction to be completed either all of the tasks should succeed or none of them can succeed; a transaction cannot be partially completed. |
| Transactional data |
|---|
| This is data that is captured when a transaction occurs. |
