Difference between revisions of "Express Entry:Best Practices"

From Melissa Data Wiki
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Express Entry|← Express Entry]]
{{CustomTOC}}
{{CustomTOC}}
==Abbreviations==
Abbreviations are used for predirectionals, such as ‘NW 5th Street’. The system will not produce a match if the client uses ‘NorthWest’ or ‘North West’.


==Matching Addresses==
Not every address will be found in Express Entry. For example, new addresses and rural addresses not serviced by the United States Postal Service may not be available. Your code should allow for the case that Express Entry does not have the submitted address and handle it appropriately. For example, you may require in your code that if the address comes up with ‘no results found’, then force the user to fill out the full address with all of line 1, city, state, and ZIP Code – and only then be able to move forward with the application. More addresses will be added in future versions including new and rural addresses.


==Allwords Search==
==When to Address Check==
When using the allwords search in CompleteAddress, matching city names may come up first in the list (the first user-entered search term will not necessarily match the street name first).
A Best Practice is to send the address through an address checker, such as Address Object, if it does not come up in Express Entry. Verifying the address using Address Object or WebSmart Web Service after attempting a match is useful in those cases that the user is required to type the whole address, since the address is unverified in this case. Also, users should know that when there is only one address showing in the results window, and this is the match, then there is no need to type further since they may choose this address with the mouse (or keyboard, depending on the implementation).


=='Official' City Name==
In the fielded query, (which uses the ExpressPostalCode service), where multiple city names are offered, choose only the ‘official’ city name. Abbreviated cities may not contain thoroughfare names.


==Sample Code Fields==
==Sample Code Fields==
In the sample code, all that is needed to access the fields that are populated by the service is the field name (for example, . Once the data entry user selects a choice from the listbox, the information is ready to place into variables.
In the sample code, all that is needed to access the fields that are populated by the service is the field name. Once the data entry user selects a choice from the listbox, the information is ready to place into variables.
 
 
==User Address Search==
The data entry user can ‘search’ for an address using backspace and entering different characters in the search box.  The service supports this feature.  Add characters to narrow the search, take away characters to broaden the search.
 


==Tab Stops==
==Tab Stops==
The sample code (VB and C#) tab stops are set in the form so that the user can use the keyboard without the mouse to use the service.
The sample code (VB and C#) tab stops are set in the form so that the user can use the keyboard without the mouse to use the service.


==Updates==
Check the product page on the Melissa Data Wiki ([[Express Entry]]) for an update on bugs and features that may be added.


==Updates==
==Fielded Search==
Check the system status page on the Melissa Data Support Web site for an update on bugs and features that may be added.
In the Fielded Search example in the sample code, it is not necessary to pass the city name. In fact,
passing the city name restricts the system to returning results only within that city. The ZIP Code is
sufficient to find the address within the system in this case.


==Free Form City==
In Free Form Entry, only the official U.S. Postal Service deliverable city names show up in a given ZIP code. This means that when entering an address, you may be given a city different than your expected city. Because of the way standardization is for addresses within the United States Postal Service and the data, the address that Express Entry returns is actually the official deliverable city for that ZIP code. Deliverability is not affected by the city being different than expected in this case.


=='Official' City Name==
==User Address Search==
In the fielded query, (which uses the CompleteZIP service), where multiple city names are offered, choose only the ‘official’ city name.  Abbreviated cities may not contain thoroughfare names.
The data entry user can ‘search’ for an address using backspace and entering different characters in the search box. The service supports this feature. Add characters to narrow the search, take away characters to broaden the search.




[[Category:Best Practices]]
[[Category:Web Services]]
[[Category:Express Entry]]
[[Category:Express Entry]]

Latest revision as of 20:37, 13 December 2016

← Express Entry


Matching Addresses

Not every address will be found in Express Entry. For example, new addresses and rural addresses not serviced by the United States Postal Service may not be available. Your code should allow for the case that Express Entry does not have the submitted address and handle it appropriately. For example, you may require in your code that if the address comes up with ‘no results found’, then force the user to fill out the full address with all of line 1, city, state, and ZIP Code – and only then be able to move forward with the application. More addresses will be added in future versions including new and rural addresses.

When to Address Check

A Best Practice is to send the address through an address checker, such as Address Object, if it does not come up in Express Entry. Verifying the address using Address Object or WebSmart Web Service after attempting a match is useful in those cases that the user is required to type the whole address, since the address is unverified in this case. Also, users should know that when there is only one address showing in the results window, and this is the match, then there is no need to type further since they may choose this address with the mouse (or keyboard, depending on the implementation).

'Official' City Name

In the fielded query, (which uses the ExpressPostalCode service), where multiple city names are offered, choose only the ‘official’ city name. Abbreviated cities may not contain thoroughfare names.

Sample Code Fields

In the sample code, all that is needed to access the fields that are populated by the service is the field name. Once the data entry user selects a choice from the listbox, the information is ready to place into variables.

Tab Stops

The sample code (VB and C#) tab stops are set in the form so that the user can use the keyboard without the mouse to use the service.

Updates

Check the product page on the Melissa Data Wiki (Express Entry) for an update on bugs and features that may be added.

Fielded Search

In the Fielded Search example in the sample code, it is not necessary to pass the city name. In fact, passing the city name restricts the system to returning results only within that city. The ZIP Code is sufficient to find the address within the system in this case.

Free Form City

In Free Form Entry, only the official U.S. Postal Service deliverable city names show up in a given ZIP code. This means that when entering an address, you may be given a city different than your expected city. Because of the way standardization is for addresses within the United States Postal Service and the data, the address that Express Entry returns is actually the official deliverable city for that ZIP code. Deliverability is not affected by the city being different than expected in this case.

User Address Search

The data entry user can ‘search’ for an address using backspace and entering different characters in the search box. The service supports this feature. Add characters to narrow the search, take away characters to broaden the search.