Configuring data in the system
In order to use IBM Relationship Resolution, you must first configure
the entity database to work with your source data.
- Configuring characteristic types
You can configure characteristic types for data that cannot be
classified as a name, number, address, or email address type. When new data
is added to a data source and you want to classify that data as a characteristic
type not already configured in the system, you need to create a new characteristic
type for the new data.
- Configuring number types
You can configure numbers types for data that can be classified
as numbers. When new data is added to a data source and you want to classify
that data as a number not already configured in the system, you need to create
a new number type for the new data.
- Configuring DQM rules
You can configure DQM rules to repair or clean up data that does
not meet minimum data quality standards. DQM rules are applied to a specific
UMF tag in a specific UMF segment.
- Configuring generic data values
You can configure data values to be generic if they exceed a configured
number of occurrences in the entity database. You can use the Visualizer to
manually define a particular value or set of values as generic, or to never
go generic.
- Configuring roles
You can configure roles to classify entities in the entity database.
Roles can be assigned to data sources or entities. Conflicting roles generate
alerts.
- Configuring role alert rules
You can configure role alert rules to define a combination of roles
that, when detected, generate alerts.
- Configuring entity types
You can configure entity types to identify the exact
nature of the entity.
- Configuring degrees of separation
You can configure IBM Relationship Resolution for up to two degrees
of separation between conflicting entities. To enable more than two degrees
of separation, you must purchase IBM Degrees of Separation for Relationship
Resolution.
- Configuring UMF documents
To successfully use Unified Messaging Format (UMF) documents, they
must be known and configured.
- Configuring the data source
You must configure a data source when there is a new data source
you want to load into the entity database.
- 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.