IM InfoSphere Identity Insight, Version 8.0

DQM function 289: Alternate name parses

DQM function 289 generates alternate name parses for incoming UMF names. By default, this function is not configured. To generate alternate name parses, you must configure the function on the <NAME> segment.

If an incoming name has alternate name parses that are different from the original name, the function creates additional <NAME> UMF segments, one segment per alternate name parse. The additional <NAME> segments are added to the UMF document.

Alternate name parses break names into different combinations of parts to provide more options for name matching during entity and relationship resolution. For example, the name of Craig Allen can be parsed into two names:
  • First name "Craig", Last name "Allen"
  • First name "Allen", Last name "Craig"
Using the same name (Craig Allen), here is an example of how the original name and the alternate name parse look in the UMF document after DQM function 289 creates the alternate name parse:

<UMF_ENTITY>
             <NAME>
                  <NAME_TYPE>M</NAME_TYPE>
                  <FIRST_NAME>Craig</FIRST_NAME>
                  <LAST_NAME>Allen</LAST_NAME>
             </NAME>
             <NAME>
                   <NAME_TYPE>ALT</NAME_TYPE>
                   <FIRST_NAME>Allen</FIRST_NAME>
                   <LAST_NAME>Craig</LAST_NAME>
             </NAME>
</UMF_ENTITY>
      

The alternate name parse is identified by the NAME_TYPE value of ALT.

Parameters

Parse Score Threshold
Indicates the minimum score that an alternate name parse must meet or exceed before the alternate parse is generated and added to the incoming UMF document.
The default value is 65.
Alternate Name Type
Indicates which NAME_TYPE value to assign to the <NAME> segment that is created by the alternate name parse.
The default value is ALT.
Attention: Make sure that the value you configure for this parameter does not match any existing NAME_TYPE values for inbound name data. If the value of the Alternate Name Type matches an existing NAME_TYPE value, the identities and entities in your database lose full attribution. Full attribution is the feature that allows entity resolution to directly associate the entity or identity with the original source system data.

Exception codes

Exception code Description Severity level
0 Alternate Parse processing was successful, and a name might have been created. 0
-1 Alternate parse failed. No alternate parses are generated. 1
-2 Creation of the alternate parse <NAME> tag failed. 3


Feedback

Last updated: 2011