There are 21 predefined name parser rules, each of which is described in this topic. The rules are applied in the order listed, which means if you disable a rule, it may have an impact on the rules that follow.
Guidelines
- It is a good idea to familiarize yourself with the terms used in the intrinsic attributes and specific attributes topics before proceeding.
- Horizontal lines are used to group related rules.
Force token following CONCATENEE to have attribute of ALPHA
(NAME_BEFORE_PATTERN_CONCATENEES_RULE1)
CONCATENEE is the attribute used to define part of a name phrase. For example, in the name MARTIN VAN BUREN, VAN is the CONCATENEE. Because the CONCATENEE is part of a name, the token that follows must comprise letters only. This rule automatically assigns the ALPHA attribute to the token.
Force concatenated token to have attribute of SURNAME
(NAME_BEFORE_PATTERN_CONCATENEES_RULE2)
A concatenated token comprises a CONCATENEE attribute followed by an ALPHA attribute. This rule assigns the specific attribute SURNAME to the concatenated token. Using the example from the preceding rule, VAN BUREN comprises the CONCATENEE and ALPHA attributes. Once this rule is applied, VAN BUREN is reassigned the SURNAME attribute.
Remove CONNECTOR between concatenated tokens
(NAME_BEFORE_PATTERN_CONCATENEES_RULE3)
A CONNECTOR is a short word used within names. This rule removes the CONNECTOR token. For example, SMITH AND JONES becomes SMITH JONES.
__________________________________________________
Force all tokens to a BUSINESS attribute, if more than one comma in a line
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE1)
If a line contains more than one comma, this rule assigns the BUSINESS attribute to all tokens on the line. For example, if a line contains the name SMITH, JONES, HOWE, AND CARTER, Inc, all tokens on the line are assigned a BUSINESS attribute.
Force all tokens to a BUSINESS attribute, if line contains a non-GENERATION numeric
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE2)
A GENERATION numeric is a qualifier that follows a name, as in JONAH SMITH, III. If the line contains a numeric that is not a GENERATION numeric, this rule assigns the BUSINESS attribute to the tokens on the line. For example, in the phrase 21 SKIDDO CLUB, 21 is a non-generation numeric, which forces the tokens on the line to BUSINESS.
Force all tokens to a BUSINESS attribute, if any business-related token is present
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE3)
This rule assigns the BUSINESS attribute to all tokens on a line if any business-related token is present. For example, if the phrase JAMES JOY, INC. appears on a line, each token on the line is assigned the BUSINESS attribute because "Inc" is a business-related token.
Force all tokens to BUSINESS attribute if ALPHA token has > 2 characters and all characters are consonants
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE4)
If an ALPHA attribute has more than two characters which are all consonants, the rule assigns a BUSINESS attribute to all the tokens on the line. For example, if the line contains SRV PLASTICS, then the rule assigns a BUSINESS attribute to every token on the line.
Force all tokens to a BUSINESS attribute, if an ALPHA-1SPECIAL token ends with an apostrophe s (’s)
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE5)
This rule assigns a BUSINESS attribute to all tokens in a line if the ALPHA1-SPECIAL attribute ends with an apostrophe s (’s). For example, if the token is JOHN’S (as in JOHN’S BAR AND GRILL), all tokens in the line are assigned a BUSINESS attribute.
__________________________________________________
Prevent BUSINESS token allocation if next or previous line contains the same SURNAME
(NAME_BEFORE_PATTERN_BUS_WORD_PROC_RULE6)
This rule prevents the CDP from assigning a BUSINESS attribute to a token if the previous or next line has a token with the same name, and that name is assigned a SURNAME attribute. For example:
JIMMY FOX
FOX NEWS
Because the first line contains a token with a SURNAME attribute (FOX) that matches a name in the second line, the second line is not assigned a BUSINESS attribute. The same rule applies to this example:
POLK EGG FARM
JIMMY POLK
__________________________________________________
Check for token splitting if there is an ALPHA-1SPECIAL token and next token is not DESCRIPTIVE
(NAME_BEFORE_PATTERN_SPLIT_WORDS_RULE1)
This rule checks for token splitting if the next token after an ALPHA-1SPECIAL is not DESCRIPTIVE. (Token splitting is the process of dividing a single token into two tokens.) For example, if the token contains MILK? (ALPHA-1SPECIAL) followed by HOOD (ALPHA), the token is not split.
Split a token if + / & is found
(NAME_BEFORE_PATTERN_SPLIT_WORDS_RULE2)
This rule splits a token into numeric and letter information if the token contains a plus sign (+), forward slash (/), or ampersand (&). For example, if the token is MARY+JOHN, this rule splits the token into three, and assigns ALPHA attributes to MARY and JOHN and an OTHER-SPECIAL attribute to the +.
__________________________________________________
Recode ALPHA-1SPECIAL token containing a hyphen (-) to an ALPHA
(NAME_LEVEL1_RULE1)
This rule reassigns an ALPHA-1SPECIAL attribute to an ALPHA attribute if the token contains a hyphen. For example, if the token contains SMITH-JONES and is assigned the ALPHA-1SPECIAL attribute, this rule tells the CDP to change the attribute assignment to ALPHA.
__________________________________________________
Skip leading B-DESCRIPTIVE, DESCRIPTIVE, RELATIONSHIP, CONNECTOR, REDEFINE, CARE-OF
(NAME_LEVEL2_RULE1)
If a line starts with a token that is assigned a B-DESCRIPTIVE, DESCRIPTIVE, RELATIONSHIP, CONNECTOR, REDEFINE, or CARE-OF attribute, this rule instructs the CDP to skip the token. For example, if the line starts with FBO, which would be assigned the RELATIONSHIP attribute, the CDP drops the RELATIONSHIP token from the pattern and moves the FBO data to the miscellaneous address data field (pr_misc_address). The resulting simpler pattern is then looked up.
Skip everything after a non-leading DESCRIPTIVE
(NAME_LEVEL2_RULE2)
This rule instructs the CDP to skip any DESCRIPTIVE that is not the first token in the pattern. For example, if the line contains descriptive words such as GENERAL FUND, the CDP ignores them and any words that follow. The dropped data is stored in the miscellaneous address data field (pr_misc_address).
Skip trailing B-DESCRIPTIVE, DESCRIPTIVE, RELATIONSHIP, CONNECTOR, REDEFINE, CARE-OF
(NAME_LEVEL2_RULE3)
If a pattern ends with a token of type B-DESCRIPTIVE, DESCRIPTIVE, RELATIONSHIP, CONNECTOR, REDEFINE, or CARE-OF, this rule instructs the CDP to skip the token. The dropped data is stored in the miscellaneous address data field (pr_misc_address).
Combined, the preceding rules in this group remove all the extra words from your name data.
Change RELATIONSHIP attribute to a CONNECTOR attribute
(NAME_LEVEL2_RULE4)
This rule changes a RELATIONSHIP attribute, such as FBO, to a CONNECTOR attribute. It has no effect on the content of the token, only on how the CDP parses the line. For example:
JOHN SMITH FBO JIMMY SMITH
GIVEN-NAME1 ALPHA RELATIONSHIP GIVEN-NAME1 ALPHA
becomes:
GIVEN-NAME1 ALPHA CONNECTOR GIVEN-NAME1 ALPHA
Set all tokens to IGNORE if an IGNORE token is identified
(NAME_LEVEL2_RULE5)
If the line contains an IGNORE attribute, this rule instructs the CDP to ignore that token and all tokens that follow on the line. Then it makes an attempt to look up the pattern with the ignore tokens still in place. If this look up fails, it removes all of the trailing IGN tokens from the line and attempts to look up the resulting IGN-less pattern. If this pattern is found it is used. This second look up does not happen unless this option is selected even if the line contains IGN tokens at the end.
For example:
JOHN SMITH DATED 1/28/1913
GIVEN-NAME1 ALPHA IGNORE DESCRIPTIVE
becomes:
GIVEN-NAME1 ALPHA
__________________________________________________
Change GIVEN-NAME1 token to an ALPHA token
(NAME_LEVEL3_RULE1)
This rule reassigns a token with a GIVEN-NAME1 attribute to an ALPHA attribute. For example:
MARY SMITH
GIVEN-NAME1 SURNAME
becomes
ALPHA SURNAME
Change SURNAME token to an ALPHA token
(NAME_LEVEL3_RULE2)
This rule reassigns a token with a SURNAME attribute to an ALPHA attribute:
MARY SMITH
GIVEN-NAME1 SURNAME
becomes
GIVEN-NAME1 ALPHA
__________________________________________________
Skip leading ALPHA-1SPECIAL, ALPHA-SPECIAL or OTHER-SPECIAL
(NAME_LEVEL4_RULE1)
This rule instructs the CDP to skip the first token on a line if it is of the type ALPHA-1SPECIAL, ALPHA-SPECIAL or OTHER-SPECIAL. The skipped data is stored in the miscellaneous address data field (pr_misc_address). For example:
Brother-in-Law JOHN SMITH
ALPHA-SPECIAL GIVEN-NAME1 ALPHA
becomes
GIVEN-NAME1 ALPHA
Skip trailing ALPHA-1SPECIAL, ALPHA-SPECIAL, NUMERIC-1SPECIAL, NUMERIC-SPECIAL or OTHER-SPECIAL
(NAME_LEVEL4_RULE2)
This rule instructs the CDP to skip the last token on a line if it is of the type ALPHA-1SPECIAL, ALPHA-SPECIAL or OTHER-SPECIAL. The skipped data is stored in the miscellaneous address data field (pr_misc_address). For example:
MARY J SMITH Sister-in-law
GIVEN-NAME1 1ALPHA ALPHA ALPHA-SPECIAL
becomes
GIVEN-NAME1 1ALPHA ALPHA