AO Consumer Match Hierarchical

Match individuals

If selected, matches records on Name and Address. If selecting more than one match criteria, records must match on more generic criteria (Family and/or Resident) to be compared as Individual. Name or First Name must be included to perform the individual match.

• Default: no

Match families

If selected, matches records on Last Name and Address. If selecting more than one match criteria, records must match on Resident to be compared as an Individual.

• Default: no

Match residents

If selected, matches records on Address only.

• Default: no

Name type

Select input name type, either Full name or Parsed name.

• Default: full name

Name

If Contact type is Full name, the name field.

• Default: blank

First name

If Contact type is Parsed name, given name (John A Smith Jr).

• Default: blank

Middle name

If Contact type is Parsed name, middle name (John A Smith Jr).

• Default: blank

Last name

If Contact type is Parsed name, surname (John A Smith Jr).

• Default: blank

Suffix

If Contact type is Parsed name, generation name (John A Smith Jr).

• Default: blank

Address type

Specify whether input address is Full address or Component address.

• Default: full address

Address1

Required if Address type is Full address. First line of unparsed address.

• Default: blank

Address2

Optional if Address type is Full address. Second line of unparsed address.

• Default: blank

Street number

Required if Address type is Component address. Street number (123 E Main Street NW Apt 101).

• Default: blank

Street predir

Required if Address type is Component address. Street predirectional (123 E Main Street NW Apt 101).

• Default: blank

Street name

Required if Address type is Component address. Street name (123 E Main Street NW Apt 101).

• Default: blank

Street suffix

Required if Address type is Component address. Street suffix (123 E Main Street NW Apt 101).

• Default: blank

Street postdir

Required if Address type is Component address. Street postdirectional (123 E Main Street NW Apt 101).

• Default: blank

City

(Required) City.

• Default: blank

State

(Required) State.

• Default: blank

ZIP

(Required) ZIP Code.

• Default: blank

Gender

Gender. Must be Male, Female, or blank (unknown or indeterminate).

• Default: blank

Record ID

(Optional) Field containing the unique record ID.

• Default: blank

Ethnic nickname match

If selected, matches less common, but valid nicknames (such as Sean/John). Unwanted nicknames can be removed by adding a "remove" entry to the Name alias table.

• Default: no

Match gender

If selected, records with two different genders (no matter how close) will never match (for example, Alexander versus Alexandra). If a full name is used instead of parsed names or a gender field is not used, Data Management will attempt to internally generate one for matching purposes.

• Default: no

Match first/middle

Select to enable cross comparison of first name against middle name.

• Default: no

Match first/initial

Select to enable cross comparison of first name against initial.

• Default: yes

Match middle/initial

Select to enable cross comparison of the middle name against initial.

• Default: yes

Ignore middle

Select to ignore middle name in name comparisons.

• Default: no

First name score

Match threshold for first name.

• Default: Medium (74)

Middle name score

Match threshold for middle name.

• Default: blank; defaults to first name score

Last name score

Match threshold for last name.

• Default: Medium (74)

Match street abbreviation

Set this to No for more exact matches. For example, 123 Brook matches 123 Brookstone with this option set to Yes.

• Default: yes

Match street missing word

Set this to No for more exact matches. For example, 123 Brook matches 123 Brook Lawn with this option set to Yes.

• Default: yes

Simple street numbers

If selected, 101A and 101 Main street are treated as identical.

• Default: no

Substring match on suite number

If selected, increases flexibility in matching of Apt/Suite # field by allowing substring matches such as 10 vs. 101.

• Default: no

Match blank/non-blank predir

Set this to No for more exact matches. For example, 123 Brook matches 123 N Brook with this option set to Yes.

• Default: yes

Match blank/non-blank postdir

Set this to No for more exact matches. For example, 123 Brook W matches 123 Brook with this option set to Yes.

• Default: yes

Match blank/non-blank suffix

Set this to No for more exact matches. For example, 123 Brook St matches 123 Brook with this option set to Yes.

• Default: yes

Match blank suite

Specifies method for matching blank Apt/Suite # input field. Options are:

• Blank Sec Ranges 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. One 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: (default) matches either case; one or both records with a blank field for Apt/Suite #.

Resolve blank suite matching conflicts

If blank matching (Blank to One Blank Only) is selected, selecting this ensures that no cascade matches will occur (No Apt to Match Apt 18, Apt 19, Apt 32, and so on).

• Default: no

Address score

Match threshold for address fields, set globally for all address components.

• Default: Tight (88)

Street number score

Optional match threshold for street number field.

• Default: blank

Street name score

Optional match threshold for street name field.

• Default: blank

Street predir score

Match threshold for Pre-directional field.

• Default: blank

Street postdir Score

Match threshold for Post-directional field.

• Default: blank

Street suffix score

Match threshold for Suffix field.

• Default: blank

Suite/Apt #/Bldg score

Match threshold for Suite/Apartment field.

• Default: blank

Match only within segment

If selected, data will be compared solely within the segment as defined below.

• Default: yes

Segment data by

Specifies method for defining sort and comparison minimums for address data. Options are:

• ZIP

• ST_NAME (ZIP + Street Name)

• ST_NUMBER (ZIP + Street Number)

• ZIP+ST_NAME+ST_NUMBER (ZIP + Street Name + Street Number) (Default)

• Custom (specify custom field below)

Street name letters

The number of letters of the street name to be used in address data segmentation. Ignored when segment type is Custom.

• Default: 3

Street number digits

The number of digits of the street number to be used in address data segmentation. Ignored when segment type is Custom.

• Default: 3

Custom segment

Optional. If Segment data by is Custom, 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

Output match info

If selected, outputs additional Match information. "Y" will generate Match Type, Group Counts/Order/Rank, Unique No., HOH Flag at the finest level. "All" will generate the same information at all levels as determined by the criteria selected (for example, Address, Phone, Email).

• Default: N

Source

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

• Default: blank

Priority

Field containing Match Rank Priority value, typically assigned using AO Define Source. Determines a record's position in a match group.

• Default: blank

Suppress flag

Field containing suppression definition for a source (value should be Y or N)

• 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

Random priority

Uses random sorting as final tie-breaker. This option may generate different results for each run. If this is option is not selected, the final tie-breaker is the input record order.

• Default: no

Tie-breaker field 1

The first field used to break priority ties.

• Default: blank

Order 1

If ASCENDING, then lower values of Tie-breaker 1 field will have higher priority.

• Default: ASCENDING

Tie-breaker field 2

The second field used to break priority ties.

• Default: blank

Order 2

If ASCENDING, then lower values of Tie-breaker 2 field will have higher priority.

• Default: ASCENDING

Tie-breaker field 3

The third field used to break priority ties.

• Default: blank

Order 3

If ASCENDING, then lower values of Tie-breaker 3 field will have higher priority.

• Default: ASCENDING

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

Name 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 following form.

where ALIAS and STANDARD are Text fields and REMOVE is Boolean. In the example above, Peg and Margie are defined as new aliases for Margaret (a blank REMOVE field is treated as FALSE), while the TRUE value in the REMOVE field explicitly suppresses Jon as an alias for John.

• Default: blank