MatchUp Object:Global Processing
Legacy/Global Usage
Foreign Character Translation
Foreign characters are translated into English equivalents. For example, “Ç” is converted to “C.” All translations are based on the assumption that your data was entered with the 1252 (Windows Latin 1) code page.
Canadian Users
MatchUp recognizes Canadian provinces and postal codes. In fact, it will abbreviate province names to their two letter abbreviation automatically.
MatchUp does handle the “QC” province abbreviation for Quebec, and “PQ” entries are automatically changed to “QC.”
In Canada, ”5-20 Main Street” means “20 Main Street, Apt 5,” but in the US, it means ”5 Main Street, Apt 20.” When deduping, MatchUp uses the contents of the ZIP/Postal code as a basis to determine a record's country of origin, and splits this type of address accordingly.
When creating matchcodes for use with Canadian Postal Codes, use the Postal Code component. However, if a database is a mix of US and Canadian records, use Zip9 as the component type. Zip9 will not adversely affect processing of Canadian records. The goal is to prevent the deduper from trying to extract a ZIP + 4 from a Canadian Postal Code.
United Kingdom Users
MatchUp can recognize United Kingdom Cities, Counties, and Postal codes. When creating matchcodes for use with United Kingdom addresses, use the Postal code (UK) component. Depending on requirements, consider using the City (UK) and County (UK) components. The Postal code component is structured in the following format: AADDIII, where AA is the Postal code Area (left justified), DD is the Postal code district (right justified), and III is the Inward Code (left justified). Extra spaces and dashes are removed as this structuring is done, so the size of this component is always 7.
Like any other matchcode component, a portion of the Postal code can always be compared by reducing its size and/or starting at a specific position. For example, starting at position 5 for a size of 3 will compare just the Inward code.
MatchUp’s street splitter will not split United Kingdom street addresses as well as Canadian and US addresses. Usually, a matchcode containing a mix of split address components and full address components is a good way to get the benefit of the street splitter (which often does perform well), along with a full-address match for backup. MatchUp Object includes the United Kingdom Address matchcode to be used as a starting point to build on.
International Users
MatchUp was designed to work with US and Canadian addresses, and performs well with addresses from other English speaking countries.
The main obstacle with international records is with the Street Splitter. Try doing a test run with one of the default matchcodes. If the street splits are not working well, use the full address when creating a matchcode instead of using the components (such as street number, street name, etc.).
Often, users have had success when combining the full address and street splitter. For example, here's an international version of one of the default matchcodes:
| Component | Size | Start | Fuzzy | Short/Empty | 1 | 2 | 3 |
|---|---|---|---|---|---|---|---|
| General | 10 | Left | No | Both Empty | X | X | X |
| Last Name | 5 | Left | No | Both Empty | X | X | X |
| First Name | 3 | Left | No | Both Empty | X | X | X |
| PO Box | 10 | Left | No | No | X | ||
| Street # | 4 | Left | No | Both Empty | X | ||
| Street Name | 4 | Left | No | No | X | ||
| Full Address | 20 | Left | No | No | X |