Release 4.3.0
Modified the architecture of OpenEMPI to solely rely on the graph database and to no longer use a relational database to store configuration information.
Added a new machine learning-based algorithm that allows the user to determine the best similarity metric (comparator) and threshold to use for a specific matching field specifically for their dataset.
Added a data standardization feature that allows the user to identify issues in their dataset and resolve them across the entire dataset
Added the ability to switch matching algorithms for a particular entity through the UI
Added a dashboard of performance related metrics to the home page of the web manager application to assist users identify resource related issues early and resolve them before they become critical
Added a scheduled task that deletes logged links from the database so that they don’t accumulate and cause resource issues after a while.
Modified the reports to not use fonts that require additional packages to be installed on some Linux distributions
Added more validation of the parameters that are used to configure transformation functions for custom fields
Upgraded numerous libraries and packages to recent versions to eliminated any security vulnerabilities that have been identified
Added the ability to rebuild individual blocking rounds instead of having to rebuild all blocking rounds at once
Added the ability to copy the blocking and matching configuration from one entity to another through the UI
Made various changes that improved the performance of the system
Release 4.2.7
Added a number of charts on the home page of the administrative application that present performance information about the instance to help administrators identify resource issues early
Upgraded a number of libraries to eliminate potential security vulnerabilities
Fixed an issue with the REST API where a request to retrieve clusters of a given size fails when a record has an identifier associated with an unknown identifier domain
Added a report that presents statistics about probable links grouped by the associated vector number
Resolved an issue with some REST API calls where they would fail to serialize the response as an XML document
...