Hi @Angelo.Panares.1

The Match NameTypes are returned from World Check. If you look at the matches below and filter by Low Quality Alias, you see WC1 identifies several matches, then click through to the details of a match and see the match was a Low Quality Alias(es) match. The schema identifies 11 enumerations for this field. - PRIMARY - AKA - AKAENHANCED - FKA - DBA - MAIDEN - LANG_VARIATION - PREVIOUS - VEHICLE_ID - LOW_QUALITY_AKA - NATIVE_AKA

Hope this helps,

Brian

click through...

    "referenceId": "e_tr_wci_1052559",
    "matchStrength": "EXACT",
    "matchedTerm": "Bush",
    "matchedNameType": "LOW_QUALITY_AKA",

Thanks. @brian.bourgault, I know about primary name, aka, low quality aka, and native.

can you confirm from which field in the data file the below are sourced?

KAENHANCED, FKA, DBA, MAIDEN, LANG_VARIATION, PREVIOUS, VEHICLE_ID,

Hi @Angelo.Panares.1,

Here is the official response from the development team:

Hope this helps,

Brian

The data model that we use to represent profiles within the WC1 API is actually quite a bit broader than World-Check’s data format. This model has been in use across all our screening products for over a decade now and has evolved to cater to many different data providers, World-Check being only one of them (it was one of the last providers we added).

The name types mentioned below may not have any mapping from World-Check data; they may only be applicable for what we are now calling “legacy” data providers such as Dow Jones data.

When clients are only interacting with World-Check data they will not need to concern themselves with these other types. These types will only be used for clients that have been migrated from Screening Online that had used legacy data providers at some point in the past.