mHUB - Lookup Settings

 

<lookup>
<keys>...</keys>
<levels>...</levels>
<outputs>...</outputs>
<advanced>...</advanced>
<maximumClusterSize>...</maximumClusterSize>
<dynamicKeys>...</dynamicKeys>
</lookup>

Lookup settings are required only if the processing mode has been set to Lookup. If these have not been specified in the configuration, then these defaults will be used:

  • two high volume match keys will be used;
  • only the individual matching level will be enabled;
  • a copy of the reference data will be output for each match.

Match Keys

<keys>
<key>PostOut + NameKey</key>
<key>PhoneticLastName + AddressKey</key>
</keys>

Refer to Matching -> Match Keys for further details.

Matching Levels

<levels>
<individual minimumScore="80" enabled="true" />
<nameOnly minimumScore="40" enabled="" />
<family minimumScore="80" enabled="" />
<address minimumScore="55" enabled="" />
<business minimumScore="80" enabled="" />
<companyOnly minimumScore="40" enabled="" />
<custom minimumScore="80" enabled="" />
</levels>

Refer to Matching -> Matching Levels for further details.

Outputs

Unlike the Matching processing mode, there is only one output type.

Lookup outputs take the form:

"|Data|Levels|IndScore|FamScore|AddScore|BusScore|CustScore|Key"

where:

  • The first character is the non-alphanumeric delimiter (note that this will not always be a pipe character);
  • "Data" is either a copy of the input data or just the unique ref (see the following Output Options);
  • "Levels" indicates which matching level(s) the data matches the lookup at;
  • "IndScore" is the total score for the individual level;
  • "FamScore" is the total score for the family level;
  • "AddScore" is the total score for the address level;
  • "BusScore" is the total score for the business level;
  • "CustScore" is the total score for the custom level;
  • "key" is a 0-based index of the match key used to find the match (e.g. if 3 match keys are defined, the index will be 1-3). Keys are numbered in the order they are defined in the configuration settings.

Refer to Matching -> Outputs for further details of "Levels".

Output Options

<outputs>
<options>
<outputUniqueRefsOnly enabled="false" />
<outputComponentScores enabled="false" />
<outputExactMatchScores enabled="false" />
<outputAllExactMatches enabled="false" />
</options>
</outputs>

outputUniqueRefsOnly: If enabled, then only unique refs are output. If disabled (the default), then the output contains a copy of the input data, which can include the unique ref.

outputComponentScores: If enabled, then scores for mapped components are output for each matching level in addition to total scores. If disabled (the default), then only the total score for each matching level is output. Refer to Matching -> Output Options for further details.

outputExactMatchScores: If enabled, then a total score is output for exact matches that is the sum of the sure score setting for all mapped components plus one. Otherwise the score field is blank for exact matches. Regardless of this setting the component scores for exact matches are always blank.

outputAllExactMatches: When disabled (the default), matching pairs are only output if a record exactly matches the first record of a cluster. If enabled, then all matching pairs are output. For example, if there are three records in a cluster (A, B, C) then three matching pairs will be found and output: A+B, A+C, B+C. Disabling this setting would prevent B+C from being output (assuming A was the first record added to the cluster). This setting should be used with care: a group containing 200 exact matches would produce 199 matching pairs by default, but with the setting enabled there'd be 19900 matching pairs!

Advanced

<advanced>
<postMatchingRules>
<rule condition="" action="" />
<rule condition="" action="" />
...
</postMatchingRules>
</advanced>

Post-Matching Rules

Refer to Matching -> Advanced Post-Matching Rules.

Other Settings

<maximumClusterSize>50000</maximumClusterSize>

maximumClusterSize: Each record added to table 2 is compared to records from table 1, by determining which cluster(s) are common to these records. If a cluster has reached the maximum size, however, then no comparisons are performed on that cluster and it will be logged as an error.

Large clusters can have a significant impact on performance. Regularly hitting the maximum cluster size usually means that the keys should be tightened; if necessary, please contact 360Science for advice.

Smart Matching

Smart Matching is a combination of features that allows the automatic configuration of keys and other settings based on columns mapped, and the automatic selection of which keys to use, on a record-by-record basis, based on the columns populated.

Smart Settings

Refer to Matching -> Smart Settings.

Dynamic Keys

Refer to Matching -> Dynamic Keys.

 

 

Was this article helpful?
0 out of 0 found this helpful

have a question or not finding what you're looking for?

Submit a ticket to get some help