A dependency is a many-to-one data relationship where the left-hand side (LHS) is composed of one or more attributes, and the right-hand side (RHS) is composed of a single attribute. One or more attributes on the LHS must always determine the attribute on the RHS within a data source.
After data is imported into a repository, examine each potential (discovered) dependency found and determine whether they are relevant to your data investigation. You can then explore dependency conflicts and export rows of dependency metadata as a .CSV file to your local or server system.
To view dependency results
- Open a data source.
- Click Summary. The Relationships table shows the number of permanent and discovered keys, dependencies, and joins in the data.
- If one or more dependencies are permanent or discovered, click the Dependencies column name to open the Dependencies tab and see all dependency metadata. To open a tab showing just those dependencies that are permanent or discovered, click a number in the Dependency column. If there are no dependencies available, a zero (0) displays and the drill-downs are unavailable.
- (Optional) Explore dependency conflicts.
- (Optional) Set relationship status to discovered or permanent.
- To delete a dependency, see Deleting Relationships.
-
Export dependency analysis from a Dependencies, Discovered Dependencies, Permanent Dependencies, or Dependency Conflicts tab. For more information, see Exporting Tab Rows.
When you review and export dependencies, the following metadata is available:
Column
Description
LH Attributes
A comma-separated list of attributes that form the left-hand side identifier for the dependency. The left-hand side (LHS) identifier can also be a single attribute.
RH Attribute
The attribute that is identified by the LHS attributes.
Status
Indicates whether the dependency has been reviewed or not.
- Discovered means not reviewed
- Permanent means reviewed as a valid dependency
Verified
Indicates whether the dependency was checked against every row of data, and therefore, whether the list of contradictions is complete.
If the original data source contains less than 10,000 rows, then this column has a value of YES because all rows were included in the initial dependency search process. The data import process samples a maximum of 10,000 during the initial dependency analysis.
Job ID
The unique schedule job number that corresponds to the column named Task ID associated with dependency-related activity in the Task Manager.
Quality %
The measure, as a percentage, of how consistently a left-hand attribute identifies the value in the right-hand attribute.
Dependencies with Quality % equal to 100 have no conflicts. Dependencies with less than 100% contain conflicts.
- Example
-
If the dependency between ORDER_NUMBER and ORDER_DATE has a Quality % equal to 99%, this indicates there is at least one row with a conflicting value, but that 99% of the values adhere to the dependency rule.
Confirming LR Values
The number of values on the LHS of the dependency that predict right-hand side (RHS) values.
Conflicting LH Values
The number of values on the LHS of the dependency that do not determine the RHS values.
Resolved %
Indicates the status, as a percentage, of the left-hand side conflicting values that have been resolved, if any.
Conflicting Rows
Total number of rows that contain a conflicting value for the RHS attribute of the dependency.
Verified Date
Date on which the dependency was last verified.
Verified By
Name of user who verified the dependency as valid.