When processing incoming name data, sometimes the gender
of a personal name can be the determining factor in whether two entities
match. Gender adds confirmation or denial weight to entity resolution
scoring to determine if two identities are the same entity.
DQM function 258 dynamically identifies the gender of the
<NAME> segment
in an incoming UMF record, creates a gender characteristic, and adds
the gender characteristic to the incoming UMF record. The gender characteristic
is added using the
<ATTRIBUTE> segment.
- If the incoming UMF record already contains a gender characteristic
in its data, DQM function 258 does not generate another gender characteristic.
- If the UMF record contains more than one <NAME> segment,
DQM function 258 creates only one gender characteristic for the entire
input record. In this case, generating multiple gender attributes
can be either redundant or conflicting.
To dynamically determine the gender of a name, ensure that at least
one UMF tag in the
<NAME> segment is configured
to use DQM function 258.
- For new product installations of V8.0 fix pack 2 or later, this
DQM function is already configured and active.
- For upgraded product versions as of V8.0 fix pack 2 or later,
this DQM function is configured but is inactive. If you want to use
this improved gender functionality, you must change the status to Active.
If you previously assigned gender using the Gender Characteristic
Type parameter of DQM function 255, reset the value of
that parameter to NONE. You can still use DQM
255 on any UMF <NAME> tag to standardize names.
You might also want to check the following configurations in the
Configuration Console:
- Ensure that the gender characteristic is configured as a confirmation
or denial in entity resolution by data source. You view or configure
this setting in the Resolution Usage field
located by selecting .
- Ensure that the gender characteristic is configured with the correct
adjustment values for entity resolution. You view or configure this
setting by selecting . Check the values of the confirmation and denial weights
assigned to the gender characteristic to be certain that they fit
your business needs.
.
Consider the following example
<NAME> segment
in this incoming UMF record:
<UMF_ENTITY>
<NAME>
<NAME_TYPE>M</NAME_TYPE>
<LAST_NAME>RASUL</LAST_NAME>
<FIRST_NAME>KARIM</FIRST_NAME>
</NAME>
.....
</UMF_ENTITY>
If DQM 258 is activated on the
<FIRST_NAME> UMF
tag of the
<NAME> segment, the incoming UMF record
looks like the following record after the gender is analyzed and created:
<UMF_ENTITY>
<NAME>
<NAME_TYPE>M</NAME_TYPE>
<LAST_NAME>RASUL</LAST_NAME>
<FIRST_NAME>KARIM</FIRST_NAME>
</NAME>
<ATTRIBUTE>
<ATTR_TYPE>GENDER</ATTR_TYPE>
<ATTR_VALUE>M</ATTR_TYPE>
</ATTRIBUTE>
.....
</UMF_ENTITY>