MatchUp Object:Config Example
; mdMatchup.cfg – the MatchUp Object configuration file example
; If you’ve ever wanted to change the behavior of how the MatchUp Object builds
; matchkeys, and dedupes records, you’ll need to understand how to edit the
; mdMatchUp.cfg file. This file is used to add, change or remove entries from
; the stock lookup tables compiled into the distributed mdMatchUp.dat file.
; For detailed definitions and usage - see the actual config file, or the documentation
; The content of this page can be used as the actual mdMatchUp.cfg file. Just save the
; unformatted text and rename to mdMatchUp.cfg. Alternately, you can just cut and paste
; the below examples into the actual file. Any line beginning with semi-colon is a
; comment, and has no effect on processing. The uncommented lines are actual
; examples of the respective mdMatchUp.dat table type.
; [Company] - List of company noise words that will be removed when creating the company
; matchcode component.
; Format is: <Company>
; <Company> = Word to remove (phrases are not allowed),(all uppercase).
; example – add GmbH, so McDonalds Corp will match McDonalds GmbH
[Company]
GMBH
; [Country] - List of countries and their abbreviations that will be used when creating the
; country portion of a matchcode.
; Format is: <Country>,<Fips>,<Iso>,<Remove>
; <Country> = Word/phrase to look up.(all uppercase)
; <Fips> = FIPS abbrevation.(all uppercase)
; <Iso> = ISO abbreviation.(all uppercase)
; <Remove> = Remove this word/phrase.
; example – because part of the country records are maintained by the International Organization for
; Standardization, we do not recommend you edit this section without contacting Melissa Data support
[Country]
; [Department] - List of title/department noise words that will be removed when created the
; title/department matchcode component.
; Format is: <Department>
; <Department> = Word to remove (phrases are not allowed),(all uppercase).
; example – adding the following will allow you to match ‘Dept of Chemistry’ to ‘Chemistry Department’
; you don’t want to add entries like ‘Education’ or ‘Chemistry’ because those are the names you are
; trying to match.
[Department]
DEPT
DEPARTMENT
; [EMail] - List of domain name substitutions that will be used when created the e-mail matchcode
; component.
; Format is: <Lookup>,<Expand>
; <Lookup> = Domain name (all uppercase).
; <Expand> = Replacement domain name (all uppercase).
; example – adding a now popular domain (not in our original list) and a possible alternate name
[EMail]
GMAIL,GMAIL.COM
GOOGLEMAIL,GMAIL.COM
; [FirstName] - List of first names (used for name splitting and genderizing).
; Format is: <Fn>, <Sex>
; <Fn> = Name to look up (all uppercase).
; <Sex> = Sex associated with the name (M=Male, F=Female, N=Neutral).
; example
[FirstName]
JATINDER,M
; [LastName] - List of last names that start with O' (used for name splitting).
; Format is: <Ln>
; <Ln> = Name to look up with the ' stripped. For example, OBRIEN (all uppercase).
; example ‘John O Jeep’ is NOT ‘John O’Jeep’ but John O. Jeep. ‘Joe O Spence’ is really ‘Joe O’Spence’
; these entries will correctly build the key with (OSPENCE) or without (O Jeep) the solitary O for last names
[LastName]
-OJEEP
OSPENCE
; [LastNamePrefix] - List of last name prefixes (ie, the "van" in "Eddie van Halen").
; Format is: <LnPre>
; <LnPre> = Last name prefix (all uppercase).
; example – This will help identify the ‘Ze’ in ‘Frank Ze Bond’ as part of the last name
[LastNamePrefix]
ZE
; [NickName] - List of first names and their corresponding nickname group. This is used when
; generating First and Middle Nickname matchcode components. Names are arranged
; in 'nickname groups' which are always truncated to 4 letters. If the name and
; its nickname group are the same, then its entry is not necessary.
; Format is: <Fn>, <Nick>
; <Fn> = Name to look up (all uppercase).
; <nick> = Four letter nickname to use.(all uppercase)
; example – this will enable Cal Ripken to match Calvin Ripken Jr
[NickName]
CALVIN,CAL
; [Prefix] - List of prefixes (used for name splitting and genderizing).
; Format is: <Prefix>, <Sex>
; <Prefix> = Prefix to look up.
; <Sex> = Sex associated with the prefix, if any (M=Male, F=Female, N=Neutral)
; example – adding the following will prevent ‘Zen Master Phil Jackson’ (he isn’t) from
; having ‘Zen’ parsed as the first name
[Prefix]
ZEN,M
MASTER,M
; [State] - List of states/provinces (used for city/state/zip splitting). Multiple-word
; states must be built-up in reverse order. For example, 'Prince Edward Island'
; must have the entries 'Island', 'Edward Island' and 'Prince Edward Island'.
; Only the complete phrase ('Prince Edward Island') should have the <st> field
; filled. Two-letter states do not need to be in this table, as they are handled
; in code.
; Format is: <state>, <St>
; <State> = State to look up (all uppercase).
; <St> = Two-letter abbreviation (all uppercase) or blank if the entry is
; not yet a real state/province.
; example – York is already in table, so working in reverse, we need to add Nueva York
[State]
NUEVA YORK,NY
;================================================================================
; WE STRONGLY RECOMMEND YOU DO NOT EDIT THIS SECTION WITHOUT FIRST
; CONSULTING MELISSA DATA SUPPORT. ADVANCED PROGRAMMING CONTENT.
;================================================================================
[Street]
; [Suffix] - List of suffixes (used for name splitting and genderizing).
; Format is: <Suffix>, <Sex>
; <Prefix> = Suffix to look up (all uppercase).
; <Sex> = Sex associated with the suffix, if any (M=Male, F=Female, N=Neutral)
; example – if the following entries are NOT added - ‘Fred Flintsone, Grand Poohbah’ will split
; incorrectly with ‘Poohbah’ occupying the last name in keybuilding
[Suffix]
GRAND,M
POOHBAH,M
; [UKCounty] - List of UK county names. Multiple-word counties must be built-up in reverse
; order in the same way they are in the [State] list.
; Format is: <Lookup>
; <Lookup> = County to look up (all uppercase).
[UKCounty]
;If we have overlooked any UK County names or alias’, please let us know.
;================================================================================
; WE STRONGLY RECOMMEND YOU DO NOT EDIT THIS SECTION WITHOUT FIRST
; CONSULTING MELISSA DATA SUPPORT. ADVANCED PROGRAMMING CONTENT.
;================================================================================
[StreetPattern]
[SecondaryPattern]
; Although you may not find the examples here practical, test them out on sample data
; to see how this alternate config file changes MatchUp Object results. And if you ever come up with
; common edits we have over-looked, please let us know, we are always trying to make the
; Object even more accurate.