Contact Zone:MatchUp:Matchcodes - Revision history

Admin at 00:32, 5 January 2017

2017-01-05T00:32:06Z

← Older revision		Revision as of 00:32, 5 January 2017
Line 1:		Line 1:
	~~[[Contact Zone:Reference\|← Contact Zone Reference]]~~		{{ContactZoneMatchUpNav}}

	{~~\| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; padding:8px 8px;"~~
	~~! style="text-align:left; color:black; border-bottom:1px solid #aaaaaa;"\|'''MatchUp Navigation'''~~
	\|-
	~~\| style="padding-right:220px;"\|~~
	\|-
	~~\|[[Contact Zone:MatchUp\|Overview]]~~
	\|-
	~~\|[[Contact Zone:MatchUp Editions\|Editions]]~~
	\|-
	~~\|[[Contact Zone:MatchUp Tutorial\|Tutorial]]~~
	\|-
	\|
	{~~\| class="mw-collapsible mw-collapsed" style="width:100%;"~~
	~~\|- align="left"~~
	~~! style="color:black;"\|[[Contact Zone:MatchUp:Component Settings\|Component Settings]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Component Settings#Show Details\|Show Details]]~~
	\|}
	\|-
	\|
	~~{\| class="mw-collapsible mw-collapsed" style="width:100%;"~~
	~~\|- align="left"~~
	~~! style="color:black;"\|MatchUp Tabs~~
	\|-
	~~\|[[Contact Zone:MatchUp:Matchcode\|Matchcode]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Field Mapping\|Field Mapping]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Options\|Options]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Source Pass-Through\|Source Pass-Through Columns]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Lookup Pass-Through\|Lookup Pass-Through Columns]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Output Filter\|Output Filter]]~~
	\|}
	\|-
	\|
	~~{\| class="mw-collapsible mw-collapsed" style="width:100%;"~~
	~~\|- align="left"~~
	~~! style="color:black;"\|[[Contact Zone:MatchUp:Matchcode Editor\|Matchcode Editor]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Matchcode Editor#Matchcode List\|Matchcode List]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Matchcode Editor#Component List\|Component List]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Component Properties\|Component Properties]]~~
	\|-
	~~\|[[Contact Zone:MatchUp:Algorithms\|Algorithms]]~~
	\|}
	\|-
	~~\|[[Contact Zone:MatchUp:Matchcodes\|Matchcodes]]~~
	\|-
	\|
	~~{\| class="mw-collapsible mw-collapsed" style="width:100%;"~~
	~~\|- align="left"~~
	~~! style="color:black;"\|Result Codes~~
	\|-
	~~\|[[Returned Result Codes:Enterprise Solutions#Contact Zone\|Returned Result Codes]]~~
	\|-
	~~\|[[Result Codes]]~~
	\|}
	\|}


	{{CustomTOC}}		{{CustomTOC}}

Admin at 20:51, 25 June 2014

2014-06-25T20:51:48Z

@@ Line 1,026: / Line 1,026: @@
 Swap matching is used to catch matches when two fields are flipped around. The most common occasion is catching the "John Smith" and "Smith John" records. But there are other uses:
-Comparing Household Records
+===Comparing Household Records===
 When there are two or three first or full names per record, a list provider may claim that every record is always "husband, wife, then children," but records will read wife then child and husband:
-CZ_MU_SM01.jpg
 In the above example, select Either component can match for Swap Pairs A, B, and C
-Comparing up to Three Address Lines
+===Comparing up to Three Address Lines===
 Although the address splitter works well in the US and Canada, some European countries can cause problems. A typical Euro-Matchcode will not use street split
 components and look at three address lines instead. The swap matching ensures that every address line is compared with every other address line.
-CZ_MU_SM02.jpg
 Again, select Either component can match for Swap Pairs A, B, and C.
-CZ_MU_SM03.jpg
 Don’t always discard the street split component matchcodes because you are working with a foreign database. Sometimes the street splitter will yield usable results.  Therefore, a combination of approaches will often work.
 [[Category:Contact Zone]]

Admin at 18:58, 25 June 2014

2014-06-25T18:58:04Z

← Older revision		Revision as of 18:58, 25 June 2014
Line 116:		Line 116:
	\|X		\|X
	\|}		\|}


	Columns 3 through 16 have been omitted for the sake of clarity.		Columns 3 through 16 have been omitted for the sake of clarity.
Line 177:		Line 178:
	\|X		\|X
	\|}		\|}


	This matchcode produced matches under the following 4 conditions:		This matchcode produced matches under the following 4 conditions:
Line 246:		Line 248:
	\|X		\|X
	\|}		\|}


	As described above, this produces the following combinations:		As described above, this produces the following combinations:
Line 271:		Line 274:
	\|Pembroke, MA 02066		\|Pembroke, MA 02066
	\|}		\|}


	The following matchcode keys would be generated:		The following matchcode keys would be generated:
Line 296:		Line 300:
	\|		\|
	\|}		\|}


	According to these matchcode keys, it is clear that these two records do not satisfy condition #1. But because blank field matching is selected, they do satisfy condition #2. The Zip/PC, Last Name, and PO Box are exactly the same. Therefore, the two records do match.		According to these matchcode keys, it is clear that these two records do not satisfy condition #1. But because blank field matching is selected, they do satisfy condition #2. The Zip/PC, Last Name, and PO Box are exactly the same. Therefore, the two records do match.
Line 338:		Line 343:
	\|X		\|X
	\|}		\|}


	The same comparison is done for combination #2, but the match is disallowed this time because the matchcode now indicates that missing (blank) information is not allowed to figure in the matching condition.		The same comparison is done for combination #2, but the match is disallowed this time because the matchcode now indicates that missing (blank) information is not allowed to figure in the matching condition.
Line 358:		Line 364:
	\|Pembroke, MA 02066		\|Pembroke, MA 02066
	\|}		\|}


	This pairing produces the following matchcode keys:		This pairing produces the following matchcode keys:
Line 383:		Line 390:
	\|456		\|456
	\|}		\|}


	This record has the same problem as before, but this time combination #1 is the cause.		This record has the same problem as before, but this time combination #1 is the cause.
Line 426:		Line 434:
	\|-		\|-
	\|}		\|}


	This is one matchcode that works well. There is one more possible tweak, however:		This is one matchcode that works well. There is one more possible tweak, however:
Line 443:		Line 452:
	\|Pembroke, MA 02066		\|Pembroke, MA 02066
	\|}		\|}


	This reflects a trend in up-scale neighborhoods, where neither street address has a Street # component, though it is very likely these records should match.		This reflects a trend in up-scale neighborhoods, where neither street address has a Street # component, though it is very likely these records should match.
Line 564:		Line 574:
	\|Company		\|Company
	\|}		\|}


	This mapping tells MatchUP that the 5-digit ZIP Code information is in a field named "CSZ" which is described as a field containing city, state, and ZIP Code information. The Last Name can be found in a field called "NAME" and is described as a full name field (which is a full name sequenced: Pre, FN, MN, LN, Suf).		This mapping tells MatchUP that the 5-digit ZIP Code information is in a field named "CSZ" which is described as a field containing city, state, and ZIP Code information. The Last Name can be found in a field called "NAME" and is described as a full name field (which is a full name sequenced: Pre, FN, MN, LN, Suf).
Line 858:		Line 869:
	\|10		\|10
	\|}		\|}


	The speed values are only rough estimates.		The speed values are only rough estimates.
Line 920:		Line 932:
	\|X		\|X
	\|}		\|}


	First name is not being used in any combination. Perhaps it was used in a combination that has since been removed from this matchcode, but is no longer necessary.		First name is not being used in any combination. Perhaps it was used in a combination that has since been removed from this matchcode, but is no longer necessary.
Line 990:		Line 1,003:
	\|X		\|X
	\|}		\|}


	Here are the four conditions for matching:		Here are the four conditions for matching:

Admin at 18:54, 25 June 2014

2014-06-25T18:54:32Z

Show changes

Admin at 23:52, 24 June 2014

2014-06-24T23:52:47Z

Show changes

Admin: Created page with "← Contact Zone Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; c..."

2014-06-24T01:18:17Z

Created page with "← Contact Zone Reference {| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; c..."

New page

[[Contact Zone:Reference|← Contact Zone Reference]]

{| class="mw-collapsible" cellspacing="2" style="background-color:#f9f9f9; border:1px solid #aaaaaa; font-size:9pt; color:#0645ad; padding:8px 8px;"
! style="text-align:left; color:black; border-bottom:1px solid #aaaaaa;"|'''MatchUp Navigation'''
|-
| style="padding-right:220px;"|
|-
|[[Contact Zone:MatchUp|Overview]]
|-
|[[Contact Zone:MatchUp Editions|Editions]]
|-
|[[Contact Zone:MatchUp Tutorial|Tutorial]]
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|[[Contact Zone:MatchUp:Component Settings|Component Settings]]
|-
|[[Contact Zone:MatchUp:Component Settings#Show Details|Show Details]]
|}
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|MatchUp Tabs
|-
|[[Contact Zone:MatchUp:Matchcode|Matchcode]]
|-
|[[Contact Zone:MatchUp:Field Mapping|Field Mapping]]
|-
|[[Contact Zone:MatchUp:Options|Options]]
|-
|[[Contact Zone:MatchUp:Source Pass-Through|Source Pass-Through Columns]]
|-
|[[Contact Zone:MatchUp:Lookup Pass-Through|Lookup Pass-Through Columns]]
|-
|[[Contact Zone:MatchUp:Output Filter|Output Filter]]
|}
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|[[Contact Zone:MatchUp:Matchcode Editor|Matchcode Editor]]
|-
|[[Contact Zone:MatchUp:Matchcode Editor#Matchcode List|Matchcode List]]
|-
|[[Contact Zone:MatchUp:Matchcode Editor#Component List|Component List]]
|-
|[[Contact Zone:MatchUp:Component Properties|Component Properties]]
|-
|[[Contact Zone:MatchUp:Algorithms|Algorithms]]
|}
|-
|[[Contact Zone:MatchUp:Matchcodes|Matchcodes]]
|-
|
{| class="mw-collapsible mw-collapsed" style="width:100%;"
|- align="left"
! style="color:black;"|Result Codes
|-
|[[Returned Result Codes:Enterprise Solutions#Contact Zone|Returned Result Codes]]
|-
|[[Result Codes]]
|}
|}

{{CustomTOC}}

Component Combinations
Every matchcode is composed of one or more possible combinations of components. These represent different possible situations in which this matchcode will detect a match between two records. A match found using any one of the combinations in a matchcode is considered a match. Programmers may think in terms of a series of OR conditions. Satisfying any one of them is considered a positive result.
MatchUp allows up to 16 different combinations of components per matchcode.
A good example of combinations would be a matchcode designed to catch last names as well as either street addresses or post office box addresses.
• Condition #1: ZIP/PC, Last Name, Street Number, Street Name
• Condition #2: ZIP/PC, Last Name, PO Box

Such a matchcode might look like this:
Component Size 1 2
ZIP/PC 5 X X
Last Name 5 X X
Street # 4 X
Street Name 4 X
PO Box 10 X
Columns 3 through 16 have been omitted for the sake of clarity. The trick to understanding this table is to look at the vertical columns of X’s. For example, looking at column 1, there are X’s in ZIP/PC, Last Name, Street #, and Street Name, indicating the goal of condition #1 exactly. In column 2 are X’s in ZIP/PC, Last Name, and PO Box, matching condition #2.

For a more advanced example:
Component Size 1 2 3 4
ZIP/PC 5 X X X X
Last Name 5 X X
Company 10 X X
Street # 4 X X
Street Name 4 X X
PO Box 10 X X
This matchcode produced matches under the following 4 conditions:
• Condition #1: ZIP/PC, Last Name, Street Number, Street Name
• Condition #2: ZIP/PC, Last Name, PO Box
• Condition #3: ZIP/PC, Company, Street Number, Street Name
• Condition #4: ZIP/PC, Company, PO Box

This matchcode could be used on a mailing list containing a mixture of both personal and company names and either street or PO Box™ addresses.

First Component Restrictions
The first component in any matchcode is special. This is the component that is used for clustering records, an essential element in efficient deduping. Thus, this component has certain restrictions placed on it. The Matchcode Editor enforces these restrictions automatically.
1. It must appear in every combination.
2. It cannot use the following types of Fuzzy matching: Containment; Frequency; Fast Near; Frequency Near; Accurate Near. All others are allowed.
3. It cannot use Initial Only matching.
4. It cannot use One Blank Field matching.
5. It cannot use Swap Matching.

[[Category:Contact Zone]]