QuickAccess verification levels (verification status) - 7.3

QAS address standardization

Version
7.3
Language
English
Product
Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Data Quality components > Standardization components > Address standardization components > QAS address standardization components
Data Quality and Preparation > Third-party systems > Data Quality components > Standardization components > Address standardization components > QAS address standardization components
Design and Development > Third-party systems > Data Quality components > Standardization components > Address standardization components > QAS address standardization components
Last publication date
2024-02-21

An address can be matched to one of six verification levels. These verification levels are directly returned by the tQASAddressRow component to indicate the returned match type of the checked addresses. Moreover, the output flows of the other QAS components are adapted to match to one or more of the below verification levels.

The six QuickAddress verification levels are:

  • Verified: The address searched upon is matched to a single deliverable address in the QuickAddress data. The verified result may be slightly different from the address entered and searched upon, as any formatting and spelling errors will have been corrected, and any missing elements will have been added. When this match type is returned, no further user interaction is required.

  • Interaction required: The address searched upon is matched to a single deliverable address in the QuickAddress data, although there is less confident about the match than for the verified level above, and therefore user interaction is recommended to confirm that it is the correct address.

  • PremisesPartial: The address searched upon is not matched to a complete deliverable result in the QuickAddress data, and instead has been matched to a partially-complete address.

    For example, the address is matched to a premises in the QuickAddress data, but a complete deliverable match could not be found: "63 Southerton Road, London" rather than "Flat A, 63 Southerton Road, London".

  • StreetPartial: The address searched upon is not matched to a complete deliverable result in the QuickAddress data, and instead has been matched to a partially-complete address.

    For example, the address is matched to a street in the QuickAddress data, but a complete deliverable match could not be found: "Kew Road, Richmond" rather than "88 Kew Road, Richmond".

  • Multiple: The address searched upon is not matched to a single deliverable result in the QuickAddress data, and instead has matched equally to more than one result.

    For example, the address is matched to two equally valid addresses that can only be distinguished by address information that has not been provided in the search.

    user interaction is therefore necessary to select the required address.

  • None: The address searched upon could not be matched to any deliverable results in the QuickAddress data. When this match type is returned, no address verification is possible and the submitted address should be used instead.