Effective in version 10.2.1, you can add one or more data domains as proximity data domains when you create or edit a data domain that has data rules or column rules. The profiling scanner scans the data source for the data domain and the proximity data domains in the resource and displays a match score in Enterprise Data Catalog. The match score is the ratio of the number of proximal data domains discovered in the data source to the number of configured proximal data domains for an inferred data domain.
Previously, you could add proximity rules to a data domain that had a data rule. If the data domains were not found in the source tables, the data conformance percentage for the data domain was reduced in the source tables by the specified value.