Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: mmarinelliNode Name: Transposed Digit Match
Node Category: Correlation
Use Case: Use this node to compare fields which contain numeric values (e.g. phone numbers, account IDs) which do may not match exactly because of data entry errors (e.g. 12345 and 12435) but logically should match.
Tested on Release: 4.1.6
External Dependencies: None
Practical Usage Example: An example use of this node has been provided in the prototype examples graph which is released in conjunction with the prototype library. Please see that graph for a executable use case.*
Node Documentation:
Functional Description:
Compares field values from two sources to determine where transposed digits are a match condition (e.g. "12345" and "12435"): "main" - all rows from the "main" input for which a match was found, "lookup" - all matched rows from the "lookup" input. The output contains a new field: "TEST_INDEX" - index of the matched set, which can be used to associate the "main" and "lookup" matched sets.
Parameters:
-
FieldNameMain: Field from "main" input which will be compared to "lookup" input
-
FieldNameLookup: Field from "lookup" input which will be compared to "main" input
-
Threshold: Maximum number of transposed digit pairs which will be considered a match
-
GroupBy: Expression used to define groups within which the matching will be performed. This narrows the computation set and thus affects performance. Default is the first character of the field value.
Known Limitations: None