You must configure a data source when there is a new data source
you want to load into the entity database.
Before you begin
In order to configure a data source, you must first set up roles.
Data sources
Data sources contain the identities that you want to process for
entity resolution and load into the entity database. Data sources contain
identifying data (unique, personal identifiers for an identity) and non-identifying
data (other attributes and data points for an identity). The identity records
in the data source must be exported as Universal Message Format (UMF) before
they can be processed by the system or loaded into the entity database. Examples
of data sources include, but are not limited to, employee lists, watch lists,
customer lists, and vendor lists.
Viewing data sources
A data source contains the data loaded into the entity database.
You may want to view existing data sources if you are planning on adding a
new data source.
Configuring a data source
To successfully load data into the entity database, you must configure
the system to recognize each data source.
Configuring the Name Manager name match level
You configure the Name Manager match level by data source,
because your name data can vary by source. The match level you select
is a comparison parameter that determines how strict the matching
is for incoming names from this data source.
Configuring data sources for enhanced name hashing
If you use enhanced name hashing, you must configure each
data source to permit name attribute candidate list building, by setting
the candidate builder configuration to the Default w/ Name
Only candidate builder.
Deleting data sources
A data source contains the data loaded into the entity database.
You may want to delete an existing data source if the data source no longer
exists, or is no longer relevant to the entity database.
Creating a data source location
To select a location to classify a data source, that location must
be configured in the system.
Turning off relationship detection
If your business requirements specify that you only need
to know who is who and not who knows who, you can reduce the amount
of processing required for each new record and speed overall system
performance by configuring relationship resolution to
only perform entity resolution and not detect relationships between
entities.