Populations and Controls

Populations and Controls

Generic Field

Generic Field

Some standard populations contain a Key Field called the
Generic_Field
, and a Match Purpose called
Generic
. Currently, this is available in the following standard populations:
  • USA
  • UK
  • AUSTRALIA
The algorithm that builds keys and search ranges for Generic Data is invoked by calling SSA-NAME3 and by passing
FIELD=Generic_Field
in the Controls parameter of the
get_keys
or
get_ranges
calls. Generic Data may contain either Person Names, Organization Names or Addresses. It may also contain a combination of these.
Using MDM - Registry Edition, it is passed in the KEY-LOGIC and SEARCH-LOGIC Controls parameters.
The
Generic_Field
algorithm is designed to overcome some of the errors and variation that are common across entities such as Names of people, Names of organizations and Addresses. For Person Name, this may include salutations and honorifics, special characters, embedded spaces, nicknames, different word orders, use of initials, spelling errors, concatenated words, localized words, and foreign words. For Organizations, this 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, and localization. For Addresses, this may include 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.
MDM - Registry Edition may pass multiple Generic Fields (such as names and addresses) in the one call to SSA-NAME3.
Generic_Field
is normally used to homogenize indexes of various types of data such as Person Names, Addresses, and Organization names. This allows them to be stored in a single index table by the application (or MDM - Registry Edition). Using such an index, application may implement a generic search where the type of data need not be available.
For example, if search for 'GreenHorn' is expected to find the person 'Peter GreenHorn', as well as the Organization 'GreenHorn Industries', then the
Generic_Field
may be used to build keys and ranges.
The Generic Match Purpose is designed to match general non-specific data. The only required field for this purpose is the
Generic_Field
.
Field
Required?
Generic_Field
Yes
Algorithms designed for specific type of data such as
Person_Names
,
Address_Part1
and
Organization_Name
carry significantly less overhead than the
Generic_Field
due to their targeted processing domain. On the other hand, the
Generic_Field
algorithm reduces the overhead associated with creation and maintenance of separate indexes, and allows applications such as MDM-Registry Edition to simplify the search experience by not having to categorize search data.
The
Generic_Field
algorithm has an Edit-List whose rules may be overridden by the Population Override Manager or Edit Rule Wizard.

0 COMMENTS

We’d like to hear from you!