MatchUp Object:Matchcode Components
Matchcode Components
The following table lists all of the available matchcode components (Data Types) in MatchUp Object.
| Component | Description |
|---|---|
| Prefix | Prefix of a personal name (Mr, Mrs, Ms, Dr). |
| First Name | A first name. |
| Middle Name | A middle name. |
| Last Name | A last name. |
| Suffix | A suffix from a personal name. |
| Gender | Male/Female/Neutral. |
| First/Nickname | A representative nickname for a first name. |
| Middle/Nickname | A representative nickname for a middle name. |
| Department/Title | A title and/or department name. *Note |
| Company | A company name. |
| Company Acronym | A company's acronym. *Note |
| Street Number | The street number from an address line3. |
| Street Pre-Directional | “South” in “3 South Main St”. |
| Street Name | The street name from an address line. |
| Street Suffix | An address suffix (St, Ave, Blvd). |
| Street Post-Directional | “North” in “3 Main St North”. |
| PO Box | PO Boxes also include Farm Routes, Rural Routes, etc. |
| Street Secondary | Apartments, floors, rooms, etc. |
| Address | A single unparsed address line. *Note |
| City | A city name. ZIP or Postal code is usually more accurate. |
| State/Province | A state or province name. |
| Zip9 | A full ZIP + 4® code (9 digits). *Note |
| Zip5 | The ZIP Code (5 digits). |
| Zip4 | The +4 extension of a ZIP + 4 code (4 digits). |
| Postal Code (Canada) | A Canadian Postal Code. |
| City (UK) | A city in the United Kingdom. |
| County (UK) | A county in the United Kingdom. |
| Postcode (UK) | A United Kingdom Postcode. |
| Country | A country. |
| Phone/Fax | A phone number. *Note |
| E-Mail Address | An e-mail address. *Note |
| Credit Card Number | A credit card number. |
| Date | A date. This may result is slower throughput! *Note |
| Numeric | A numeric field. This may result is slower throughput! *Note |
| Proximity | Allows you to specify a maximum distance in miles between records in which a match will be possible. This may result is slower throughput! *Note |
| General | Any general information. ID, birthday, SSN, etc. |
Global Components
| Component | Description |
|---|---|
| Postal Code | (Zip &/ plus 4) Complete postal code for a particular delivery point. |
| Premises Number | (Street Number) Alphanumeric indicator within premises field. |
| Double Dependent Locality | Smallest population center data element |
| Dependent Locality | (Urbanization) Smaller population center data element. Dependent on Locality. |
| Sub Administrative Area | (County) Smallest geographic data element. |
| Sub National Area | Arbitrary administrative region below that of the sovereign state. |
| Locality | (City) Most common population center data element. |
| Administrative Area | (State) Most common geographic data element. |
| Thoroughfare Leading Type | Leading thoroughfare type indicator within the Thoroughfare field. |
| Thoroughfare Pre-Directional | (Street Pre Direction) Prefix directional contained within the Thoroughfare field. |
| Thoroughfare Name | (Street Name) Name indicator within the Thoroughfare field |
| Thoroughfare Trailing Type | (Street Suffix) Trailing thoroughfare type indicator within the Thoroughfare field. |
| Thoroughfare Post-Directional | (Street Post Direction) Postfix directional contained within the Thoroughfare field. |
| Dependent Thoroughfare Pre-Directional | Prefix directional contained within the Dependent Thoroughfare field. |
| Dependent Thoroughfare Leading Type | Leading thoroughfare type indicator within the Dependent Thoroughfare field. |
| Dependent Thoroughfare Name | Name indicator within the Dependent Thoroughfare field |
| Dependent Thoroughfare Trailing Type | Trailing thoroughfare type indicator within the Dependent Thoroughfare field. |
| Dependent Thoroughfare Post-Directional | Postfix directional contained within the Dependent Thoroughfare field. |
Notes
Company, Company Acronym, Department/Title
Frequently these components don't match exactly because of ‘noise words’ such as “the,” “and,” “agency,” and so on. MatchUp strips these words from these components.
Company Acronym
MatchUp Object converts any multi-word company name into an acronym(for example, “International Business Machines” is squeezed into “IBM”). Single-word company names are left as they are. This conversion is done after noise words are removed.
Street Address Components
The seven street address components (Street Number, Street Pre-Directional, Street Name, Street Suffix, Street Post-Directional, PO Box, Street Secondary) are obtained by splitting up to three address lines. Note that PO Box and/or Street Secondary do not have to appear on their own line, or in a particular field. MatchUp's proprietary “street smart” splitter does all of the work.
Full Address
When using the Full Address component, you are at the mercy of every little deviation in data entry. Because MatchUp Object’s street splitter is so powerful, it is preferable to use street address components instead of the Full Address in nearly all cases. The only exception may be when processing foreign addresses that don’t conform very well to US, Canadian or UK addressing formats.
Zip9, Zip5, Zip4, Canadian Postal Code
MatchUp Object removes dashes and spaces from ZIP codes. When processing a mix of Canadian Postal Codes and US ZIP codes, use the Zip9 component.
Phone Number
MatchUp Object removes non-numeric characters from phone numbers. Leading ‘1-’ and trailing extensions are stripped if present. Numbers lacking an area code are right justified so that the local dialing code and number are aligned with numbers having area codes. If a data table often has missing or inaccurate area codes (i.e., after a recent area code split), start at the 4th position of the phone number component. Do not use the right most 7 positions, as badly formatted extensions can sometimes cause the phone number to get coded improperly.
E-Mail Address
MatchUp Object removes illegal characters from e-mail addresses. Incomplete, changed, and commonly misspelled domain names are corrected using the Email Address data table.
Date
MatchUp Object allows you to specify a number of days for which a match will be possible if the records being compared fall within the set number of days apart.
Numeric
This allows you to specify an integer number for which a match will be possible if the record’s unit difference falls within the set number.
Proximity
The proximity component requires you to map in Latitude / Longitude coordinates(Not determined by MatchUp. Can be determined by a product such as GeoCoder or Contact Verify) allowing you to match addresses within a maximum distance setting for this component.