Any dependency conflicts found during dependency discovery or creation are shown in a Conflicts: Selected Dependency tab. Dependency conflicts occur when values on the left-hand side (LHS) of the dependency do not determine the right-hand side (RHS) values. Exploring dependency conflicts helps identify which dependencies are relevant to your project. To explore the reasons why a conflict may exist, drill down to the actual rows where the conflicts exist. The results may determine whether to save a dependency as permanent. You can export dependency conflicts and data rows that contain the conflicts.
The Quality % metadata shows the measure, as a percentage, of how consistently a left-hand attribute (Lh Attr) identifies the value in the right-hand attribute (Rh Attr). Dependencies with Quality % equal to 100 have no conflicts. Dependencies with less than 100% contain conflicts.
- Conflict Example:
-
The post code 75227 should always indicate the city of Dallas. If there is an occurrence in your data of the city being something other than Dallas (such as Dllas) with that particular post code, then the Discovery Center shows this as a conflict to the dependency. You can then drill-down to view the conflicting data rows and decide whether this is an issue. If a dependency is relevant to your analysis, you can save it (set to permanent).
To explore conflicting dependency values