Selecting the Matching Critical Data fields
The following critical data fields are selected as default values for person matching.
When a critical data field is selected, the value of the configuration element is set to true. Otherwise, it is set to false.
| Name | Configuration Element Name | Default Values |
|---|---|---|
| Address | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonAddress/enabled | TRUE |
| City | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonCity/enabled | TRUE |
| State/Province | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonState/enabled | TRUE |
| Country | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonCountry/enabled | TRUE |
| County | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonNationalID/enabled Note: The
following two configuration elements are related and have to be set
to proper values.
|
TRUE |
| Zip/Postal Code | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonPostCode/enabled | TRUE |
| BirthDate | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonBirthDate/enabled | TRUE |
For organization matching the default data fields are listed in the following table.
| Name | Configuration Element Name | Default Values |
|---|---|---|
| Address | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgAddress/enabled | TRUE |
| City | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgCity/enabled | TRUE |
| State/Province | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgState/enabled | TRUE |
| Country | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgCountry/enabled | TRUE |
| County | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgNationalID/enabled Note: :
The following two configuration elements are related and have to be
set to proper values.
|
TRUE |
| Zip/Postal Code | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgPostCode/enabled | TRUE |
| Established Date | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgEstablishedDate/enabled | TRUE |
The data fields in the preceding table are the default values used for matching.
There are four configuration options for Match Strings (4 for Person and 4 for Org), each Match String contains three pieces of data. For example, for person match string 1, the configuration elements are:
- /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString1/enabled – Contains true or false depending on the client choice
- /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/ PersonMatchString1/type – Contains I or C. I indicates that the Party Identification entity is used in the match string. C indicates that the Party Contact Method is used as the match string.
- /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/ PersonMatchString1/TpCd – Contains the type of either Identifier (identifier.id_tp_cd) or Contract Method (CONTACTMETHODGROUP. CONT_METH_TP_CD).
The match string type can either be party identification or party contact method, as shown in sample data in the following table.
| Party Identifiers | Party Contact Methods |
|---|---|
| Social Security Number | Home Telephone |
| Driver's License Number | Business Telephone |
| Birth Certificate | Facsimile |
| Social Insurance Number | Pager |
| Tax Identification Number | Cellular |
| Tax Registration Number | Business Email |
| Passport Number | Personal Email |
| Health Card | Mobile Telephone |
For party identifiers, the type/value pairs are from CDIDTP table in data base. For party contact methods, the type/value pairs can be found in CDCONTMETHTP table. As there are four match string configurations provided for each Person or Organization. A maximum of four combined strings from party identification and contact methods can be selected for each Person or Organization.
The person match string configuration elements are listed in the following table:
| Person match strings | Configuration elements name |
|---|---|
| Person matchString1 | /BM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString1/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString1/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString1/type |
| Person matchString2 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString2/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString2/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString2/type |
| Person matchString3 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString3/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString3/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString3/type |
| Person matchString4 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString4/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString4/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Person/PersonMatchString4/type |
The organization match string configuration elements are listed in the following table.
| Organization match strings | Configuration elements name |
|---|---|
| Organization matchString1 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString1/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString1/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString1/type |
| Organization matchString2 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString2/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString2/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString2/type |
| Organization matchString3 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString3/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString3/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString3/type |
| Organization matchString4 | /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString4/enabled /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString4/TpCd /IBM/ELMDM/IIS/CriticalDataFieldsMatch/Org/OrgMatchString4/type |