Unify and manage your data

Objectives

Objectives Contents

About objectives

Administer system

Model data

Data modeling at a glance

Data modeling operation

Define hierarchies

Define entity types and attributes

Define relationships

Configure Interaction types

Create new graph types

Configure grouping types

Managing Object Deletion and Activeness

Define crosswalks for data sources

Crosswalks

Configuring surrogate keys

Crosswalk Patterns

Managing Crosswalk Dates

Manage reference data

Configure the Reltio UI

Load and export data

Stream data

Cleanse data

Integrate data

Monitor data quality

Resolve potential matches

Manage profiles

Manage workflow tasks

Explore data insights

Crosswalk Patterns

You can define Crosswalk patterns for structuring data from source systems.

Data from Source systems can be structured in a number of ways. As an example, the address data for an HCP (Individual) could be provided as follows:

1:1 Flat file with each row containing the HCP details as well as the address. If multiple HCPs worked at the same address, the address data would be repeated for each HCP.
1:M relational data with two tables, one for the HCP and one for ADDRESS. If multiple HCPs worked at the same address, there would be one entry in the ADDRESS table, and the Foreign Key in the HCP table would reference the Primary Key of the relevant address in ADDRESS.
M:M relational data with three tables, one for the HCP, one for the ADDRESS and an intersection table for the HCP_ADDRESS containing the PKs of both the HCP and ADDRESS tables. This approach is used when an HCP can be associated with multiple addresses. If multiple HCPs worked at the same address, there would be one entry in the ADDRESS table, one entry in the HCP table and the HCP_ADDRESS table would contain one record with the FKs from both the other tables for each HCP.