5.9.4 Good Guy Attributes

The system will generate a hash code to capture the current state of attributes on the WL side based on EDQ configuration.

When a name event/match is taking place, and the Last Updated Date with fingerprinting option is selected as Yes.

If there is no change to the Last Updated Date field, then this is considered positive for good guy (match will be considered good guy if all other conditions are met).

If there is a change to the Last Updated Date field, then the hashcode will be compared. If they are identical, then this is considered positive for a good guy (match will be considered good guy if all other conditions are met).

The following fields are used for hashcode calculation:

  1. WL - entities - prepared data:
    • dnListKey (e.g. "DJW")
    • dnListSubKey (e.g. "DJW-SAN" or "DJW-EDD")
    • dnListRecordType (e.g. "SAN" or "EDD")
    • dnListRecordId (e.g. "1044689")
    • dnOriginalEntityName
    • dnEntityName
    • dnPrimaryName
    • dnOriginalScriptName
    • dnAddress
    • dnCity
    • dnState
    • dnAddressCountryCode
    • dnAddressCountry
    • dnAllCountries
    • dnAllCountryCodes (e.g. "RU")
  2. WL - individuals - prepared data
    • dnListKey (e.g. "DJW")
    • dnListSubKey (e.g. "DJW-SAN" or "DJW-EDD")
    • dnListRecordType (e.g. "SAN" or "EDD")
    • dnListRecordId (e.g. "1044689")
    • dnOriginalFullName
    • dnOriginalGivenNames
    • dnOriginalFamilyName
    • dnFullName
    • dnGivenNames
    • dnFamilyName
    • dnPrimaryName
    • dnOriginalScriptName
    • dnAddress
    • dnCity
    • dnState
    • dnAddressCountryCode
    • dnAddressCountry
    • dnAllCountries
    • dnAllCountryCodes (e.g. "RU")
  • The fields used for hash code calculation should be configurable by consulting as global configuration (1 set of fields).
  • This configuration cannot be changed per list type.
  • This is expected to be a 1-time activity that will happen during implementation.

This functionality is expected to work for all types of lists - 3rd party lists and internal lists. This means an analyst should be able to mark a good guy based on an internal list match.