Origin
On this page
- Merging records by identifiers
- Linking golden records
- Understanding origin in identity resolution
- Impact on identity resolution
- Linking records using origin
- Common configuration considerations
- Useful resources
Generally, the origin determines the source of a golden record. So, when you map your data, the origin will be automatically set to the name of the data source, for example, MicrosoftDynamics, Oracle, Hubspot, or MsSQLDatabase5651651. However, you can change the origin during mapping if needed.
As mentioned in our Identifiers reference article, the origin is used in the primary identifier and the identifiers.
In this article, we’ll explain the usage of the origin in two important processes in CluedIn:
Merging records by identifiers
Since the origin is used in the primary identifier and the identifiers, it plays a role in merging—when 2 identifiers are identical, the records will merge together.
To understand the role of origin in merging, suppose you have an attribute that you can safely rely on to merge records across source systems. Let’s say this attribute is a SerialNumber that is used in your CRM, ERP, and Support systems. As the serial number is unique and cross-system, you can use it to merge together all golden records that have the same serial number. Of course, you can achieve this using our UI; however, there is a faster way to do this via merging by identifiers.
Let’s consider the example of three records, each coming from a different source system—CRM, ERP, and Support. For each data source, we select the Serial Number to produce the primary identifier. The following table shows the identifiers that will be produced by default.
| Source | Business domain | Origin | Primary identifier |
|---|---|---|---|
| CRM | Product | crm | /Product#crm:[SERIAL NUMBER VALUE] |
| ERP | Product | erp | /Product#erp:[SERIAL NUMBER VALUE] |
| Support System | Product | support | /Product#support:[SERIAL NUMBER VALUE] |
Even if the serial number is the same, the records will not merge together as the origin of each record is different.
So, how would you use the serial number to merge records together? The answer is by producing an identifier that shares the same origin, for example, PRODUCT-SERIALNUMBER. As a result, the identifier for each record will share the same business domain, origin, and the value of serial number as shown in the following table.
| Source | Business domain | Origin | Primary identifier |
|---|---|---|---|
| CRM | Product | PRODUCT-SERIALNUMBER | /Product#PRODUCT-SERIALNUMBER:[SERIAL NUMBER VALUE] |
| ERP | Product | PRODUCT-SERIALNUMBER | /Product#PRODUCT-SERIALNUMBER:[SERIAL NUMBER VALUE] |
| Support System | Product | PRODUCT-SERIALNUMBER | /Product#PRODUCT-SERIALNUMBER:[SERIAL NUMBER VALUE] |
Since the origin is shared among different sources, each time the same serial number for a product is sent to CluedIn, it will be merged.
Linking golden records
Origin can be used to link golden records together to create relationship. You can link golden records using identifiers, rules, or manually in the UI. To create a relationship using identifiers, you need to know the origin of target golden records. These are the golden records to which you want to link current records.
Suppose you have Contact records that contain the companyID property, and you know that you have Company records with this ID. To establish a link between Contact and Company, you need to define the “to” relationship by setting up the following:
- Business domain:
/Company - Origin:
[ORIGIN-OF-COMPANY-RECORDS] - Value:
Company ID
The combination of those 3 values needs to match one of the identifiers of target records.
To make the process of linking golden records easier, you can use the recommendation for defining the origin that we provided in Merging by identifiers. Essentially, the method of shared origin that you use for merging by identifiers can also be used to facilitate the process of linking golden records. This way you do not have to rely on the source system and instead use the origin that you defined for related data.
Understanding origin in identity resolution
Origin is a component of the entity identifier and defines the namespace in which identifier values are interpreted.
An entity identifier in CluedIn is composed of:
- Business domain
- Origin
- Value
Example
/Organization#CRM:123
/Organization#ERP:123
In this example, the value 123 represents two different identifiers because the origin differs.
Impact on identity resolution
Origin is used as part of identifier matching during entity resolution.
Origin determines:
- the identity boundary for a given data source
- how identifier values are interpreted within that boundary
If the same origin and value are used across records, they are treated as the same identifier and may result in merging.
If the origin differs, the identifiers are treated as distinct, even when the value is identical.
Linking records using origin
Origin is also used when linking records across business domains.
To create a relationship using identifiers, the following must match:
- Business domain
- Origin
- Value
This combination must correspond to an identifier on the target record.
Common configuration considerations
Using the same origin for multiple systems
Using a shared origin across systems allows records with matching identifier values to be treated as the same identifier.
This approach should only be used when identifier values are consistent and represent the same logical entity across systems.
Using different origins for the same system
Using multiple origins for the same logical source may prevent matching and result in duplicate entities.
Using unstable origins
Origins derived from dynamic values (for example, file names or timestamps) can lead to inconsistent identity resolution and duplicate records.
Origins should remain stable and represent a logical source system.