Scenario Comparison Matrix

The six samples demonstrate different strategies for integrating address management into a website.
This table summarises the key features and how they differ between the scenarios.
  Address Capture Address Verification Key Search Rapid Addressing:
Standard, Single Line
Typical user and environment Customer on a website.
Also useful for casual users on an intranet (self-service application).		 Customer on a website. Often useful in countries where users prefer to verify a complete address. Trained operator on an intranet or browser-based application.
Secondary search method using Key data to retrieve addresses.		 Trained operator on an intranet or browser-based application.
Entry of other people's addresses.
How it fits into existing address entry process Requires additional pages to guide the user through the capture process. Sits behind existing address entry form. Interaction with user only required when the address cannot be verified as correct. Requires additional pages to guide the user through the capture process. Typically integrated as a pop-up window that appears on top of the main application (activated via a key or link).
Entry of address information to be searched upon Separate page prompts user for key elements of the address. If the postal code is not known then alterative prompts are shown. Entered into existing address entry form. The user enters a Key value instead of address elements to search on Typedown mode prompts for key elements in reverse order.
Single Line mode allows free-form entry of one or more address elements.
Key Search mode allows searching on a Key value.
Data selection Separate page prompts user to pick from a list of configured datamaps. Can be omitted if only a single datamap is supported. Provided by the underlying address entry form. If not defined then a default datamap can be assumed. User can select from a list of defined datamaps or can be omitted if only a single datamap is supported. User selects from a list of defined datamaps at the same time as entering the initial search.
Use of picklists to display multiple matches A simple picklist of all deliverable addresses, each displaying every element of the address. As for the capture scenario. If minimal user interaction is required then this stage can be dropped.  When keys match multiple addresses a picklist will be displayed The user drills-down through a series of picklists, each time narrowing down the search. Only relevant elements of the address are displayed at each level.
Ability to enter text to refine picklists The user simply clicks on the required address. The user is prompted for extra address information according to the content of the picklist.
Display of percentage match scores Scores are not shown, in order to simplify interaction with the user. No scores required as Key value either a full match  or no match. Single Line mode displays these at the first picklist level. These are not seen if an automatic step-in occurs.
Postal code recode and bordering locality warning messages Warnings are not shown, in order to simplify interaction with the user. Not Applicable This is to flag to the user that key elements of the search address have been altered.
Display of picklist history Multiple levels of picklist are not supported. All selected picklist items (including automatic step-ins) are displayed at the top of the picklist.
Use of informational prompts (in picklist) Informationals are not shown, in order to simplify interaction with the user. Used to manage long picklists. Also used to accept unrecognised premise or sub-premise information.
Maximum number of displayed matches Picklist displays a maximum of 250 matches
(SLMaxMatches setting).		 1st picklist level in Single Line mode displays a maximum of 250 matches (SLMaxMatches setting). All other picklists display an informational prompt when there are more than 50 matches (UPIThreshold setting).
Automatic step-in to a single exact match (100%) A picklist is not displayed if a single exact match occurs. This is not applicable as picklists are only shown if the address cannot be verified. A picklist is not displayed if a single exact match occurs. This can apply to multiple picklists, stepping all the way through to the final address.
Warning to step-back to view close matches (after an automatic step-in) This is to simplify the interaction with the user. Automatic step-ins do not occur. This is to simplify the interaction with the user. This is more important given the entry of other people's addresses and the likely omission of key address information.
Entry of unrecognised premise or sub-premise information The user selects a suitable address and performs any modifications on the address confirmation page. All entered information is retained unless otherwise overridden by the user. Not Applicable. Entering this information as picklist refinement text results in the informational prompt "Address not recognised (click to override)".
Address confirmation page This can be dropped, if passing the address through to an alternative page which allows address modification. Interaction with the user is not required for addresses that are verified as correct. This can be dropped, if passing the address through to an alternative page which allows address modification. This can normally be dropped, as the underlying application will receive the formatted address. Note that some warning messages will be lost.
Use of advanced search functionality Wildcard characters (* and ?) are supported but not generally used. The verification engine is designed to take a complete address. Wildcards are not supported Wildcard characters (* and ?) and tags (@) are supported in Single Line mode.
Re-configurable prompt sets Please contact QAS Support if you require alternative prompt sets to those supplied as standard. The format of the input address can be configured or constrained as required. See the user guide for more details. This is not applicable given that input is via a single-line prompt.
Support for names data Only supported under the intranet scenarios. Names are returned via an additional picklist (on selecting a premise or sub-premise).
Support for business data Only supported under the intranet scenarios. The additional business information is merged in with the postal data.
Support for DataPlus sets Configured and returned as part of the formatted address.
Use of partner sourced data Use either the built in prompt sets or over-ride them. Consult your manual for instructions. Interaction with user only required when the address cannot be verified as correct. Not Available Using fielded prompt sets, Single Line searches can be performed.
Click here to return to the C# .NET Samples home page.