are optional parameters that you can include to specify the scope of address validation. You can configure these parameters to specify the level of address matching that you want Informatica AddressDoctor Cloud to do while validating an address.
The
MatchingScope
parameter defines the level of granularity to which Informatica AddressDoctor Cloud validates an address. The
MatchingAlternatives
parameter specifies whether to consider alternate names while validating an address.
You can set the
MatchingScope
parameter to specify which address elements that you want Informatica AddressDoctor Cloud to validate. You can set the matching scope to locality, street, or delivery-point level. The default value of
MatchingScope
is ALL so that Informatica AddressDoctor Cloud validates all possible elements including locality, street, and delivery-point elements in the input address. You receive the best results if you set
MatchingScope
to ALL as Informatica AddressDoctor Cloud validates all possible elements. If you do not want Informatica AddressDoctor Cloud to consider some of the address elements for validation, you can set
MatchingScope
to a value other then ALL.
If the reference address database does not contain the specified level of information, Informatica AddressDoctor Cloud validates only those elements that the database contains.
You can configure Informatica AddressDoctor Cloud to validate address elements based on synonyms or alternate names that are available in the reference address database. Synonyms of an address element include alternate names of a place or a street. For example, vanity names in the U.S. addresses. The archival name of an address element refers to an outdated name of a place or street.
To match input address elements with synonyms or archival names that are available in the reference address database, set
MatchingAlternatives
to SYNONYM_ONLY, ARCHIVE_ONLY, or ALL. The default value of
MatchingAlternatives
is ALL. You can set
MatchingAlternatives
to NONE if you do not want Informatica AddressDoctor Cloud to consider synonyms or archival names when it validates an address.
You can set one of the following values for
MatchingScope
:
LOCALITY_LEVEL
. To ignore information other than the Locality and Postal Code information while validating the address.
STREET_LEVEL
. To validate up to the street information including the street name along with the LOCALITY_LEVEL elements. If you set
MatchingScope
to STREET_LEVEL, Informatica AddressDoctor Cloud ignores information such as house number and subbuilding.
DELIVERYPOINT_LEVEL
. To validate up to the delivery point information including house number and post box number and ignore further elements such as building, subbuilding, and organization.
ALL
. To validate all elements, including street, locality, and delivery point information, that Informatica AddressDoctor Cloud can validate.
You can include
MatchingAlternatives
to suppress the use of historical and synonym and exonym data for matching address elements. You can set one of the following values for
MatchingAlternatives
:
NONE
SYNONYM_ONLY
ARCHIVE_ONLY
ALL
Note that the actual scope of address validation is dependent on the corresponding country database.