Express Entry:Best Practices: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Express Entry|← Express Entry]] | [[Express Entry|← Express Entry]] | ||
{{CustomTOC}} | |||
==Matching Addresses== | ==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. | 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== | ==When to Address Check== | ||
A Best Practice is to send the address through an address checker 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). | A Best Practice is to send the address through an address checker 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== | =='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. | 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. 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. | ||
==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== | ==Updates== | ||
Check the product page on the Melissa Data Wiki ([[Express Entry]]) for an update on bugs and features that may be added. | 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== | ==User Address Search== | ||
The data entry user can ‘search’ for an address using backspace and entering different characters in the search box. | 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. | ||
==Abbreviations== | |||
Addresses in Express Entry have certain rules about abbreviations. Express Entry has abbreviations for words in addresses, always uses those abbreviations, and the user must be aware of when to use them or a match will not occur. For instance in the address, ‘1001 E 20th Ave’, one can see the predirectional, ‘E’, is abbreviated from ‘East’, the ordinal street name ‘20th’ is abbreviated from ‘Twentieth’, and suffix ‘Ave’ is abbreviated from ‘Avenue.’ Any other representation of this address will not be in Express Entry Data. Postdirectionals are abbreviated as well, such as the ‘N’ in ‘US Highway 27 N’. Note that in this case ‘Highway’ is not abbreviated ‘Hwy’ as in other addresses, due to it being part of the street name and not an ordinal. By following these guidelines, one can produce more matches within Express Entry. | |||
[[Category: | [[Category:Web Services]] | ||
[[Category:Express Entry]] | [[Category:Express Entry]] | ||
Revision as of 19:30, 19 February 2015
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 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.
Abbreviations
Addresses in Express Entry have certain rules about abbreviations. Express Entry has abbreviations for words in addresses, always uses those abbreviations, and the user must be aware of when to use them or a match will not occur. For instance in the address, ‘1001 E 20th Ave’, one can see the predirectional, ‘E’, is abbreviated from ‘East’, the ordinal street name ‘20th’ is abbreviated from ‘Twentieth’, and suffix ‘Ave’ is abbreviated from ‘Avenue.’ Any other representation of this address will not be in Express Entry Data. Postdirectionals are abbreviated as well, such as the ‘N’ in ‘US Highway 27 N’. Note that in this case ‘Highway’ is not abbreviated ‘Hwy’ as in other addresses, due to it being part of the street name and not an ordinal. By following these guidelines, one can produce more matches within Express Entry.