MatchUp Object:Global Processing - Revision history

Admin at 19:28, 4 January 2019

2019-01-04T19:28:00Z

← Older revision		Revision as of 19:28, 4 January 2019
Line 3:		Line 3:
	{{CustomTOC}}		{{CustomTOC}}

	==Legacy/~~Domestic~~ Usage==		==Legacy/Global Usage==
	===Foreign Character Translation===		===Foreign Character Translation===
	Foreign characters are translated into English equivalents. For example, “Ç” is converted		Foreign characters are translated into English equivalents. For example, “Ç” is converted

Admin at 19:26, 4 January 2019

2019-01-04T19:26:54Z

← Older revision		Revision as of 19:26, 4 January 2019
Line 2:		Line 2:

	{{CustomTOC}}		{{CustomTOC}}

	~~==Global Processing==~~
	~~===Supported Countries===~~
	~~{\| class="alternate01 sortable"~~
	~~!Country!!ISO 3166-1 alpha-2 Code~~
	~~\|- style="vertical-align:top;"~~
	~~\|Australia\|\|AU~~
	\|-
	~~\|Austria\|\|AT~~
	\|-
	~~\|Canada\|\|CA~~
	\|-
	~~\|Chile\|\|CL~~
	\|-
	~~\|Denmark\|\|DK~~
	\|-
	~~\|Germany\|\|DE~~
	\|-
	~~\|Mexico\|\|MX~~
	\|-
	~~\|The Netherlands\|\|NL~~
	\|-
	~~\|New Zealand\|\|NZ~~
	\|-
	~~\|Sweden\|\|SE~~
	\|-
	~~\|Switzerland\|\|CH~~
	\|-
	~~\|United Kingdom\|\|UK~~
	\|-
	~~\|United States of America\|\|US~~
	\|}


	~~===Beta Countries===~~
	~~{\| class="alternate01 sortable"~~
	~~!Country!!ISO 3166-1 alpha-2 Code~~
	\|-
	~~\|Iceland\|\|IS~~
	\|-
	~~\|Norway\|\|NO~~
	\|-
	~~\|Spain\|\|ES~~
	\|}


	==Legacy/Domestic Usage==		==Legacy/Domestic Usage==

Admin at 19:36, 13 February 2017

2017-02-13T19:36:07Z

← Older revision		Revision as of 19:36, 13 February 2017
Line 6:		Line 6:
	===Supported Countries===		===Supported Countries===
	{\| class="alternate01 sortable"		{\| class="alternate01 sortable"
	!~~Released Countries~~		!Country!!ISO 3166-1 alpha-2 Code
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\|AT		\|Australia\|\|AU
	\|-		\|-
	\|AU		\|Austria\|\|AT
	\|-		\|-
	\|CA		\|Canada\|\|CA
	\|-		\|-
	\|CH		\|Chile\|\|CL
	\|-		\|-
	\|CL		\|Denmark\|\|DK
	\|-		\|-
	\|DE		\|Germany\|\|DE
	\|-		\|-
	\|DK		\|Mexico\|\|MX
	\|-		\|-
	\|MX		\|The Netherlands\|\|NL
	\|-		\|-
	\|NL		\|New Zealand\|\|NZ
	\|-		\|-
	\|NZ		\|Sweden\|\|SE
	\|-		\|-
	\|UK		\|Switzerland\|\|CH
	\|-		\|-
	\|US		\|United Kingdom\|\|UK
			\|-
			\|United States of America\|\|US
	\|}		\|}


			===Beta Countries===
	{\| class="alternate01 sortable"		{\| class="alternate01 sortable"
	!~~Beta Countries~~		!Country!!ISO 3166-1 alpha-2 Code
	\|-		\|-
	\|ES		\|Iceland\|\|IS
	\|-		\|-
	\|IS		\|Norway\|\|NO
	\|-		\|-
	\|NO		\|Spain\|\|ES
	\|}		\|}

Admin at 18:30, 13 February 2017

2017-02-13T18:30:17Z

← Older revision		Revision as of 18:30, 13 February 2017
Line 8:		Line 8:
	!Released Countries		!Released Countries
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\|DE		\|AT
	\|-		\|-
	\|AT		\|AU
	\|-		\|-
	\|UK		\|CA
	\|-		\|-
	\|CH		\|CH
	\|-		\|-
	\|CA		\|CL
			\|-
			\|DE
	\|-		\|-
	\|CL		\|DK
	\|-		\|-
	\|AU		\|MX
	\|-		\|-
	\|NL		\|NL
			\|-
			\|NZ
			\|-
			\|UK
	\|-		\|-
	\|US		\|US
Line 31:		Line 37:
	!Beta Countries		!Beta Countries
	\|-		\|-
	\|MX		\|ES
	\|-		\|-
	\|DK		\|IS
	\|-
	~~\|NZ~~
	\|-		\|-
	\|IS		\|NO
	\|}		\|}

Admin at 17:18, 8 September 2016

2016-09-08T17:18:40Z

@@ Line 3: / Line 3: @@
 {{CustomTOC}}
-==Foreign Character Translation==
+==Global Processing==
 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
 (Windows Latin 1) code page.
-==Canadian Users==
+===Canadian Users===
 MatchUp recognizes Canadian provinces and postal codes. In fact, it will abbreviate
 province names to their two letter abbreviation automatically.
@@ Line 25: / Line 64: @@
 is to prevent the deduper from trying to extract a ZIP + 4 from a Canadian Postal Code.
-==United Kingdom Users==
+===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)
@@ Line 45: / Line 84: @@
 starting point to build on.
-==International Users==
+===International Users===
 MatchUp was designed to work with US and Canadian addresses, and performs well with
 addresses from other English speaking countries.

Admin: Admin moved page MatchUp Object:International Users to MatchUp Object:Global Processing

2016-09-08T16:59:02Z

Admin moved page MatchUp Object:International Users to MatchUp Object:Global Processing

← Older revision	Revision as of 16:59, 8 September 2016
(No difference)

Admin at 18:41, 25 November 2014

2014-11-25T18:41:35Z

← Older revision		Revision as of 18:41, 25 November 2014
Line 1:		Line 1:
	~~<!--__FORCETOC__-->~~		[[MatchUp Object\|← MatchUp Object]]

	{{CustomTOC}}		{{CustomTOC}}

Admin: Admin moved page International Users to MatchUp Object:International Users without leaving a redirect

2014-11-25T18:29:31Z

Admin moved page International Users to MatchUp Object:International Users without leaving a redirect

← Older revision	Revision as of 18:29, 25 November 2014
(No difference)

Admin: Created page with " {{CustomTOC}} ==Foreign Character Translation== Foreign characters are translated into English equivalents. For example, “Ç” is converted to “C.”..."

2012-09-11T16:38:36Z

Created page with " {{CustomTOC}} ==Foreign Character Translation== Foreign characters are translated into English equivalents. For example, “Ç” is converted to “C.”..."

New page

{{CustomTOC}}

==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:

{|class="alternate01" cellspacing="0"
!Component!!Size!!Start!!Fuzzy!!Short/Empty!!1!!2!!style="border-right:0px;"|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
|}

[[Category:MatchUp Object]]