The Preloading_Type attribute controls if preloading is done. The following preloading types are available.

• NONE. No preloading (default)
• PARTIAL. Loads the metadata and indexing structures into memory. Offers some performance enhancements and is an alternative when there is insufficient memory to fully load the entire databases.
• FULL. Loads the entire reference database into memory. Offers significant performance enhancements for large data volumes.

AddressDoctor supports four different validation types specified as the Database Type element. For use with DataMigrator, the BATCH mode is used.

• BATCH. The Correction Only type is used for batch processing. It is optimized for speed and terminated processing when ambiguous data is encountered that cannot be corrected automatically.
• INTERACTIVE. This type is used in interactive environments to generate suggestions when address data is ambiguous.
• FASTCOMPLETION. Used in quick address entry applications. It allows it input of truncated data and generate suggestions for input.
• CERTIFIED. For the US and Canada addresses can be processed in compliance with a certification scheme.
• PARSE. Used for separating address input into token for subsequent processing in other systems.
• COUNTRYRECOGNITION. Used when some input data lacks country information which is necessary for successful processing, identifies records missing this data.

Addresses have developed differently in different countries, cultures, and languages around the world. AddressDoctor uses mapping to describe the different parts of an address. However, the generic names they use do not always correspond to American usage. The following table shows this:

AddressDoctor	American Usage	Example
Country	Country	United States
Province	State	Georgia
Locality	City	Atlanta
Street	Street	Hammond Drive, NE
House Number	Number	980
Building	Building	Two Lakeside Commons
Sub Building	Floor, Suite, Apartment, and so on	Suite 1200
Delivery Service	P.O. Box, RFD, and so on
Postal Code	Zip Code	30328
Organization	Organization, Company, and so on	Information Builders
Department	Department, Division	Southern Sales
Contact	Addressee

AddressDoctor	American Usage	Example
Organization	Organization, Company, etc.	Information Builders
Department	Department, Division	Southern Sales
Contact	Addressee

AddressDoctor can process address data in a wide variety of formats.

Databases containing addresses typically contain fields for each part of the address. However, information in address databases can be entered in the wrong field address parsing is needed to assign data to the correct field. AddressDoctor implements a parsing engine that is independent of postal reference data.

The Optimization_Level attribute controls how AddressDoctor behaves in respect to input data fields, the following types are available.

• NARROW. The parser will honor input assignment strictly, with the exception of separation of Street Number from Street information.
• STANDARD. The parser will separate address element more actively, for example:
  • Province will be separated from Locality information.
  • PostalCode will be separated from Locality information.
  • House Number will be separated from Street information.
  • SubBuilding will be separated from Street information.
  • DeliveryService will be separated from Street information.
  • SubBuilding will be separated from Building information.
  • Locality will be separated from PostalCode information.
• WIDE. Parser separation will happen similarly to STANDARD, but additionally up to 10 parsing candidates will be passed to validation for processing. Validation will widen its search tree and take additional reference data entries into account for matching.

For each address processed. AddressDoctor provides a status code in the field PROCESSSTATUS. The meanings of these codes are shown in the table below.

V4	Verified - Input data correct - all (postal relevant) elements were checked and input matched perfectly.
V3	Verified - Input data correct on input but some or all elements were standardized or input contains outdated names or exonyms.
V2	Verified - Input data correct but some elements could not be verified because of incomplete reference data.
V1	Verified - Input data correct but the user standardization has deteriorated deliverability (wrong element user standardization - for example, postcode length chosen is too short). Not set by validation.
C4	Corrected - all (postal relevant) elements have been checked.
C3	Corrected - but some elements could not be checked.
C2	Corrected - but delivery status unclear (lack of reference data).
C1	Corrected - but delivery status unclear because user standardization was wrong. Not set by validation.
I4	Data could not be corrected completely, but is very likely to be deliverable - single match (for example, HNO is wrong but only 1 HNO is found in reference data).
I3	Data could not be corrected completely, but is very likely to be deliverable - multiple matches (for example, HNO is wrong but more than 1 HNO is found in reference data).
I3	Data could not be corrected, but there is a slim chance that the address is deliverable.
I1	Data could not be corrected and is pretty unlikely to be delivered.
N1	Validation Error: No validation performed because country was not recognized.
N2	Validation Error: No validation performed because required reference database is not available.
N3	Validation Error: No validation performed because country could not be unlocked.
N4	Validation Error: No validation performed because reference database is corrupt or in wrong format.
N5	Validation Error: No validation performed because reference database is too old - please contact AddressDoctor to obtain updated reference data.
S4	Parsed perfectly.
S3	Parsed with multiple results.
S2	Parsed with errors - elements changed position.
S1	Parse error - input format mismatch.