The Algorithm that builds keys and search ranges for Person Names is invoked by a calling SSANAME3 by passing

FIELD=Person_Name

in the Controls parameter of the "get keys" or "get ranges" calls.

The

Person_Name

Algorithm is designed to overcome the error and variation that would be typically found in a person’s full name. This may include salutations and honorifics, special characters, embedded spaces, nicknames, different word orders, use of initials, spelling errors, concatenated words, localized words, foreign words, etc.

An application should pass the full person name to SSA-NAME3 functions. The word order, i.e. the position of the first name, middle names and family names, should be the normal word order used in your data population. For example, in English speaking countries, the normal word order would be:

First Name + Middle Name(s) + Family Name(s)

Depending on your table design, your application may have to concatenate these separate fields into one field before calling SSA-NAME3.

While SSA-NAME3 includes Search Strategies that overcome word order variations, the word order does have some significance in the quality of Narrow and Typical searches, and when matching using the Purposes "same Household", "same Family" or "same Wide_Household".

The application (or SSA-NAME3) may pass multiple names (such as a married name and a former name) in the one call to SSA-NAME3.

The

Person_Name

algorithm has an Edit-List whose rules may be overridden by the Population Override Manager or Edit RuleWizard.

The Algorithm that builds keys and search ranges for Organization Names is invoked by a calling application by passing

FIELD=Organization_Name

or

FIELD=Organisation_Name

in the SSANAME3 Controls parameter of the "get keys" or "get ranges" calls.

The

Organization_Name

Algorithm is designed to overcome the error and variation that would be typically found in a business, company, institution or other organization name. The Algorithm also caters for multiple names in the one field, and a mixture of Organization and Person names in the data population. The error and variation may include different legal endings, abbreviations, salutations and honorifics, special characters, embedded spaces, nicknames, different word orders, missing and extra words, spelling errors, concatenated words, use of initials, mixed use of numbers and words, foreign words, localization, etc.

This field supports matching on a single name, or a compound name (such as a legal name and its trading style).

The application (or SSA-NAME3) may also pass multiple names (such as a current name and a former name) in the one call to SSA-NAME3.

The

Organization_Name

algorithm has an Edit-List whose rules may be overridden by the Population Override Manager or Edit Rule Wizard.

The Algorithm that builds keys and search ranges for Addresses is invoked by a calling application by passing

FIELD=Address_Part1

in the SSA-NAME3 Controls parameter of the "get keys" or "get ranges" calls.

The

Address_Part1

Algorithm is designed to overcome the error and variation that would be typically found in addresses. The error and variation may include the presence of care of information, abbreviations, special characters, embedded spaces, different word orders, spelling errors, concatenated words and numbers, use of initials, mixed use of numbers and words, foreign words, missing words, extra words and sequence variations, etc.

An application should pass the part of address up to, but not including, the locality "last line". The word order, i.e. the position of the address components, should be the normal word order used in your data population. These should be passed in one field. Depending on your table design, your application may need to concatenate these attributes into one field before calling SSA-NAME3.

For example, in the US, a typical string to pass would comprise of:

Care-of + Building Name + Street Number + Street Name + Street Type + Apartment Details

But not including City, State, Zip, Country.

The application (or SSA-NAME3) may pass multiple addresses (such as a residential address and a postal address) in the one call to SSA-NAME3. See the

API REFERENCE

manual for more details.

The

Address_Part1

algorithm has an Edit-List whose rules may be overridden by the Population Override Manager or Edit Rule Wizard.