AO Business Name-Only Match

Business name

Required. Company name used for matching. Default: Blank.

Business name 2

Optional. Alternate company name that can also be used for cross-field matching (for example, Lotus & IBM). Allows for different companies to be matched to either field. Default: Blank.

Business keyword

Optional. Firm keyword that is matched using a separate score. This should be used in conjunction with a separate parsing step that separates the significant parts of a business name from "common" parts. For example, suppose that you have the following business names:

FIRST NATIONAL BANK OF MIAMI

1ST NATL BANK MIAMI

FIRST NATIONAL BANK OF ORLANDO

BANK OF MIAMI

The key words here are “MIAMI” and “ORLANDO”.  Using upstream regular expressions and the text parsing tools, you can create a separate KEYWORD field that contains the distinguishing parts of a business name, and specify this field as the Business keyword. 

If you specify this field, also configure the Business keyword matching score on the Match tab. Default: Blank.

Record ID

Optional. Field containing the unique record ID. Default: Blank.

Business score

Match threshold for business name field after any optional business adjustments (described below) are taking into account. Default: Tight (88).

Match nicknames

Allows for personal names in a firm to be standardized. For example, in Liz Smith Enterprises versus Elizabeth Smith Enterprises, Liz and Elizabeth would be treated as identical. Default: No.

Match initials

If selected, enables Initials match option. Default: No.

Initials

Recover match points if Initial matches a name (for example, J Robin Smith Inc versus Jonathon Robert Smith, Inc). Default: Treat as Similar (75).

Match abbreviations

If selected, enables Abbreviations match option. Default: No.

Abbreviations

Recover match points due to an abbreviation identified by pattern rather than known value (for example, Halbert Construction Contractors versus Hlbrt Construction Contractors). Default: Treat as Similar (75).

Match acronyms

If selected, enables Acronyms match option. Default: No.

Acronyms

Assign acronym matches a specific score for their part of the match (for example, International Machine Parts versus IMP). Default: Treat as Similar (75).

Missing words

Recover match points due to missing or disjoint words (for example, Halston Construction Contractors versus Halston Contractors). Default: Treat as Similar (75).

Strip vowels if > N bytes

If selected, allows for fewer comparisons on large firm words by eliminating the vowels and comparing only the vowels within the word. Default: 7.

Keyword score

Match threshold for business keyword field after optional business Keyword adjustments (described below) are taken into account. Default: Blank.

Match blank keyword

Specifies method for matching blank business keyword input field. Options are:

Blanks Never Match: If either or both records have blank field, they will not match.

Blank vs. Blank Only: If both records have blank field, they will match. If only one is blank, they will not match.

Blank vs. Non Blank Only: If only one record has blank field, they will match. If both have blank field, they will not match.

Both One Blank and Both Blanks Match: Matches either case; one or both records with a blank field for Business keyword.

Default: Blank vs. Blank Only.

Match abbreviations

Allows for variations in the business keyword field (for example, MISS vs. MISSISSIPPI to be considered an exact match as a case of abbreviation). Default: No.

Business letters

Allows for segmentation of data based on the first X characters of the business name. This option allows for better performance; however it may reduce the number of potential matches. Default: 0.

Max segment size

Maximum number of records compared in a single comparison group. The default setting allows for nearly-unlimited segment size. If you want to limit segment size to avoid runaway computation, potentially at the expense of missing a few record matches, set this to a lower value like 1000. Typically you can reduce this value unless you are matching within a very large segment like STATE. Default: 99999.

Custom segment

Optional. If segmentation other than above is desired, select the field containing the segment key. Default: Blank.

Output match score

If selected, outputs the overall score from the match records as a percentage between 1—100. Default: No.

Source

Field containing the logical description for input data source. This is usually defined in AO Define Source. Default: Blank.

Internal dedupe flag

Field containing a Y/N flag indicating whether or not data from a particular source should be compared against itself (deduped) or solely against other sources. As a general rule, master databases are not internally deduped whereas update files are. Default: Blank.

Compare sources not internally deduped

If a matching process has more than one source with the internal dedupe field set to "N", selecting this will compare the two sources. Default: Yes.

Parallelism level

Set to the lesser of the number of CPU cores on the Execution Server, or the number of threads configured in the project in which the macro is embedded. Default: 1.

Optimize for large segments

If you receive warnings like "Window Compare segment size for value (06828EAS3135) has exceeded 2000," enable this option. Comparing large candidate groups may reduce matching efficiency. Selecting this option increases the number of records that can be sent to a matching process without slowing processing. Default: No.

Business alias table

Path and name of optional DLD table used to augment or override the alias values defined within the macro. The table must be of the form:

where ALIAS and STANDARD are Text fields and REMOVE is Boolean. In the example above, Paving and Hotmix are defined as new aliases for Asphalt (a blank REMOVE field is treated as FALSE), while the TRUE value in the REMOVE field explicitly suppresses Reproduction as an alias for Copying. Default: Blank.

Business noise table

Path and name of optional DLD table used to add additional "noise" words for Firm matching. The table must be a single-column DLD table of the form:

where WORDS is a Text field. The example above shows data that shouldn’t contribute to the match score because it is contextually meaningless. If you are matching financial institutions, word BANK could be a "noise" word. Default: Blank.