Tim at 21:17, 19 February 2014

2014-02-19T21:17:07Z

← Older revision		Revision as of 21:17, 19 February 2014
Line 10:		Line 10:
	<nowiki/>; For detailed definitions and usage - see the actual config file, or the documentation <br>		<nowiki/>; For detailed definitions and usage - see the actual config file, or the documentation <br>

	<nowiki/>; The content of this ~~file~~ can be used as the actual mdMatchUp.cfg file. Just save the <br>		<nowiki/>; The content of this page can be used as the actual mdMatchUp.cfg file. Just save the <br>
	<nowiki/>; unformatted text and rename to mdMatchUp.cfg. Alternately, you can just cut and paste <br>		<nowiki/>; unformatted text and rename to mdMatchUp.cfg. Alternately, you can just cut and paste <br>
	<nowiki/>; the below examples into the actual file. Any line beginning with semi-colon is a <br>		<nowiki/>; the below examples into the actual file. Any line beginning with semi-colon is a <br>

Tim at 21:16, 19 February 2014

2014-02-19T21:16:15Z

← Older revision		Revision as of 21:16, 19 February 2014
Line 25:		Line 25:

	<nowiki/>; example – add GmbH, so McDonalds Corp will match McDonalds GmbH <br>		<nowiki/>; example – add GmbH, so McDonalds Corp will match McDonalds GmbH <br>
	Company] <br>		[Company] <br>
	GMBH <br>		GMBH <br>

Tim: Created page with "; mdMatchup.cfg – the MatchUp Object configuration file example
; If you’ve ever wanted to change the behavior of how the MatchUp Object bui..."

2014-02-19T21:15:28Z

Created page with "<nowiki/>; mdMatchup.cfg – the MatchUp Object configuration file example <nowiki/>; If you’ve ever wanted to change the behavior of how the MatchUp Object bui..."

New page

<nowiki/>; mdMatchup.cfg – the MatchUp Object configuration file example 

<nowiki/>; If you’ve ever wanted to change the behavior of how the MatchUp Object builds 
<nowiki/>; matchkeys, and dedupes records, you’ll need to understand how to edit the 
<nowiki/>; mdMatchUp.cfg file. This file is used to add, change or remove entries from 
<nowiki/>; the stock lookup tables compiled into the distributed mdMatchUp.dat file. 

<nowiki/>; For detailed definitions and usage - see the actual config file, or the documentation 

<nowiki/>; The content of this file can be used as the actual mdMatchUp.cfg file. Just save the 
<nowiki/>; unformatted text and rename to mdMatchUp.cfg. Alternately, you can just cut and paste 
<nowiki/>; the below examples into the actual file. Any line beginning with semi-colon is a 
<nowiki/>; comment, and has no effect on processing. The uncommented lines are actual 
<nowiki/>; examples of the respective mdMatchUp.dat table type. 

<nowiki/>; [Company] - List of company noise words that will be removed when creating the company 
<nowiki/>; matchcode component. 
<nowiki/>; Format is: <Company> 
<nowiki/>; <Company> = Word to remove (phrases are not allowed),(all uppercase). 

<nowiki/>; example – add GmbH, so McDonalds Corp will match McDonalds GmbH 
Company] 
GMBH 

<nowiki/>; [Country] - List of countries and their abbreviations that will be used when creating the 
<nowiki/>; country portion of a matchcode. 
<nowiki/>; Format is: <Country>,<Fips>,<Iso>,<Remove> 
<nowiki/>; <Country> = Word/phrase to look up.(all uppercase) 
<nowiki/>; <Fips> = FIPS abbrevation.(all uppercase) 
<nowiki/>; <Iso> = ISO abbreviation.(all uppercase) 
<nowiki/>; <Remove> = Remove this word/phrase. 

<nowiki/>; example – because part of the country records are maintained by the International Organization for 
<nowiki/>; Standardization, we do not recommend you edit this section without contacting Melissa Data support 
[Country] 

<nowiki/>; [Department] - List of title/department noise words that will be removed when created the 
<nowiki/>; title/department matchcode component. 
<nowiki/>; Format is: <Department> 
<nowiki/>; <Department> = Word to remove (phrases are not allowed),(all uppercase). 

<nowiki/>; example – adding the following will allow you to match ‘Dept of Chemistry’ to ‘Chemistry Department’ 
<nowiki/>; you don’t want to add entries like ‘Education’ or ‘Chemistry’ because those are the names you are 
<nowiki/>; trying to match. 
[Department] 
DEPT 
DEPARTMENT 

<nowiki/>; [EMail] - List of domain name substitutions that will be used when created the e-mail matchcode 
<nowiki/>; component. 
<nowiki/>; Format is: <Lookup>,<Expand> 
<nowiki/>; <Lookup> = Domain name (all uppercase). 
<nowiki/>; <Expand> = Replacement domain name (all uppercase). 
<nowiki/>; example – adding a now popular domain (not in our original list) and a possible alternate name 
[EMail] 
GMAIL,GMAIL.COM 
GOOGLEMAIL,GMAIL.COM 

<nowiki/>; [FirstName] - List of first names (used for name splitting and genderizing). 
<nowiki/>; Format is: <Fn>, <Sex> 
<nowiki/>; <Fn> = Name to look up (all uppercase). 
<nowiki/>; <Sex> = Sex associated with the name (M=Male, F=Female, N=Neutral). 

<nowiki/>; example 
[FirstName] 
JATINDER,M 

<nowiki/>; [LastName] - List of last names that start with O' (used for name splitting). 
<nowiki/>; Format is: <Ln> 
<nowiki/>; <Ln> = Name to look up with the ' stripped. For example, OBRIEN (all uppercase). 

<nowiki/>; example ‘John O Jeep’ is NOT ‘John O’Jeep’ but John O. Jeep. ‘Joe O Spence’ is really ‘Joe O’Spence’ 
<nowiki/>; these entries will correctly build the key with (OSPENCE) or without (O Jeep) the solitary O for last names 
[LastName] 
-OJEEP 
OSPENCE 

<nowiki/>; [LastNamePrefix] - List of last name prefixes (ie, the "van" in "Eddie van Halen"). 
<nowiki/>; Format is: <LnPre> 
<nowiki/>; <LnPre> = Last name prefix (all uppercase). 

<nowiki/>; example – This will help identify the ‘Ze’ in ‘Frank Ze Bond’ as part of the last name 
[LastNamePrefix] 
ZE 

<nowiki/>; [NickName] - List of first names and their corresponding nickname group. This is used when 
<nowiki/>; generating First and Middle Nickname matchcode components. Names are arranged 
<nowiki/>; in 'nickname groups' which are always truncated to 4 letters. If the name and 
<nowiki/>; its nickname group are the same, then its entry is not necessary. 
<nowiki/>; Format is: <Fn>, <Nick> 
<nowiki/>; <Fn> = Name to look up (all uppercase). 
<nowiki/>; <nick> = Four letter nickname to use.(all uppercase) 

<nowiki/>; example – this will enable Cal Ripken to match Calvin Ripken Jr 
[NickName] 
CALVIN,CAL 

<nowiki/>; [Prefix] - List of prefixes (used for name splitting and genderizing). 
<nowiki/>; Format is: <Prefix>, <Sex> 
<nowiki/>; <Prefix> = Prefix to look up. 
<nowiki/>; <Sex> = Sex associated with the prefix, if any (M=Male, F=Female, N=Neutral) 

<nowiki/>; example – adding the following will prevent ‘Zen Master Phil Jackson’ (he isn’t) from 
<nowiki/>; having ‘Zen’ parsed as the first name 
[Prefix] 
ZEN,M 
MASTER,M 

<nowiki/>; [State] - List of states/provinces (used for city/state/zip splitting). Multiple-word 
<nowiki/>; states must be built-up in reverse order. For example, 'Prince Edward Island' 
<nowiki/>; must have the entries 'Island', 'Edward Island' and 'Prince Edward Island'. 
<nowiki/>; Only the complete phrase ('Prince Edward Island') should have the <st> field 
<nowiki/>; filled. Two-letter states do not need to be in this table, as they are handled 
<nowiki/>; in code. 
<nowiki/>; Format is: <state>, <St> 
<nowiki/>; <State> = State to look up (all uppercase). 
<nowiki/>; <St> = Two-letter abbreviation (all uppercase) or blank if the entry is 
<nowiki/>; not yet a real state/province. 

<nowiki/>; example – York is already in table, so working in reverse, we need to add Nueva York 
[State] 
NUEVA YORK,NY 

<nowiki/>;================================================================================ 
<nowiki/>; WE STRONGLY RECOMMEND YOU DO NOT EDIT THIS SECTION WITHOUT FIRST 
<nowiki/>; CONSULTING MELISSA DATA SUPPORT. ADVANCED PROGRAMMING CONTENT. 
<nowiki/>;================================================================================ 
[Street] 

<nowiki/>; [Suffix] - List of suffixes (used for name splitting and genderizing). 
<nowiki/>; Format is: <Suffix>, <Sex> 
<nowiki/>; <Prefix> = Suffix to look up (all uppercase). 
<nowiki/>; <Sex> = Sex associated with the suffix, if any (M=Male, F=Female, N=Neutral) 

<nowiki/>; example – if the following entries are NOT added - ‘Fred Flintsone, Grand Poohbah’ will split 
<nowiki/>; incorrectly with ‘Poohbah’ occupying the last name in keybuilding 
[Suffix] 
GRAND,M 
POOHBAH,M 

<nowiki/>; [UKCounty] - List of UK county names. Multiple-word counties must be built-up in reverse 
<nowiki/>; order in the same way they are in the [State] list. 
<nowiki/>; Format is: <Lookup> 
<nowiki/>; <Lookup> = County to look up (all uppercase). 
[UKCounty] 
<nowiki/>;If we have overlooked any UK County names or alias’, please let us know. 

<nowiki/>;================================================================================ 
<nowiki/>; WE STRONGLY RECOMMEND YOU DO NOT EDIT THIS SECTION WITHOUT FIRST 
<nowiki/>; CONSULTING MELISSA DATA SUPPORT. ADVANCED PROGRAMMING CONTENT. 
<nowiki/>;================================================================================ 
[StreetPattern] 
[SecondaryPattern] 

<nowiki/>; Although you may not find the examples here practical, test them out on sample data 
<nowiki/>; to see how this alternate config file changes MatchUp Object results. And if you ever come up with 
<nowiki/>; common edits we have over-looked, please let us know, we are always trying to make the 
<nowiki/>; Object even more accurate.

MatchUp Object:Config Example - Revision history

Tim at 21:17, 19 February 2014

Tim at 21:16, 19 February 2014

Tim: Created page with "; mdMatchup.cfg – the MatchUp Object configuration file example ; If you’ve ever wanted to change the behavior of how the MatchUp Object bui..."

Tim: Created page with "; mdMatchup.cfg – the MatchUp Object configuration file example
; If you’ve ever wanted to change the behavior of how the MatchUp Object bui..."