Released: June 2022
This release contains the following new features:
The following algorithms were added:
Phonetic full text: An algorithm best used for strings. It can recognize the phonetic equivalent of two words spelled differently using the Beider-morse phonetic tokens. The comparator takes into account the synonyms and stop words defined in the data model.
Hybrid fuzzy: An algorithm best used for string and text data types. It can capture complex relationships between two field values by automatically customizing transformations for a given criterion. Points of note about this algorithm:
Does not return a 100% matching score on synonyms.
Strings that are similar, but contain characters like spaces or dashes do not return a 0% matching score.
When strings fall within the acceptable distance score they are not considered as the exact same. For example, a distance of 1 returns .95, a distance of 2 returns .9, etc.
A script task was added to run a matching operation from a workflow.
Fields can now have a weight of 0. Setting the weight to 0 excludes the fields from the pre-processing phase.
An API was added to check whether the add-on has any ongoing background operations.
When upgrading from version 3.0.0, 3.1.0, or 3.1.1 you must update existing matching configurations. After updating configuration settings, you should re-execute matching to ensure that matching related metadata is up to date.
The options to specify what happens after a merged record is modified were removed. Now, the following behavior is applied when a record is in the merged state and the modified field:
Is not configured to use in matching operations: The add-on executes an automatic merge using the settings defined in the default matching policy's merge policy.
Is configured to use in matching operations: The record is changed to the <unset> state.
This release contains no changes to third-party libraries.
This release contains the following closed issues:
[MAME-7455] The Evaluate matching and Run match services return inconsistent results.
[MAME-7479] There is conflict between the Evaluate matching and See details results.
[MAME-7542] Results cannot display after running Evaluate matching on a display with 1920X1080 resolution at 150% zoom.
This release contains the following known issues:
[MAME-7434] Linked records are duplicated in the link table when one of the foreign keys is not part of the primary key.
When matching using the foreign key option, you can only specify a single hop foreign key. In other words, it cannot be a foreign key to a foreign key.
The Validation service in the Consolidated view runs as expected when first executed, but slow on subsequent executions.
In order to accurately track record lineage, table history must remain activated over time. If the table's activation status repeatedly changes, the lineage data will be inconsistent.
Severe errors occur when multiple datasets based on the same model exist and a table from one of these datasets is activated in an add-on matching configuration. As a workaround, you can create another data model publication using the Manage publications service in the Data Model Assistant. After creating a dataset for the new publication, you can follow the normal procedures to configure a matching policy for tables in the new dataset.
For foreign key alignment, the FKs that are multi-value fields cannot be aligned (either manually or automatically).