Validating Potential Dependencies - trillium_discovery - trillium_quality - Latest

Trillium Control Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
Latest
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
Copyright
2024
First publish date
2008
Last updated
2024-10-18
Published on
2024-10-18T15:02:04.502478

Potential dependencies are dependencies that you already know exist in your data. For example, you may have a list of attributes that are potentially dependent on each other, but you do not know the quality of the dependencies (how consistently the LHS attributes indicate the RHS attribute) and need to evaluate these.

You can run a process that allows you to identify potential dependencies and validate their LHS and RHS attribute relationships. The attributes you select for validation will be marked as permanent dependencies.

To validate potential dependencies

  1. Do one of the following:
    • On the Home tab: Select Keys/Deps > Create.
    • In the Navigation View: Right-click an entity and select Create Key or Dependency.
    • In the Navigation View: From the Analysis tab, right-click Dependencies and select Create Dependency or right-click a Baseline Analysis project and select Analyze > Create Key or Dependency.

    The Create Key or Dependency window opens.

  2. Select Dependencies.
  3. From the drop-down list, select the entity in which you are interested.
  4. Click Next.
  5. Enter a Job Name.
  6. Place a checkmark beside each left-hand (LHS) attribute you want to validate.
  7. Place a checkmark beside the one right-hand (RHS) attribute you want to validate.
  8. Click Finish.
  9. Run the analysis now or schedule a time for the job to run later.
  10. In the Navigation View, click the Analysis tab, expand Dependencies, and expand Permanent Dependencies.
  11. Double-click the entity name used in the dependency job to view results in a List View.
    Note: If you find potential dependencies missing, re-run the dependency analysis using different analysis criteria.