About Dependency Analysis - trillium_discovery - trillium_quality - 17.2

Trillium Control Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Quality
Trillium > Trillium Discovery
Version
17.2
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
First publish date
2008
Last updated
2024-07-01
Published on
2024-07-01T08:56:48.630530

A dependency is a many-to-one data relationship where one or more attributes determine the value of another attribute within a single entity. After data is imported into a repository, review the results by examining each potential dependency found.

There are two types of dependencies:

  • Discovered—found as a potential dependency but not yet reviewed for validity.
  • Permanent—reviewed and verified.

A discovered dependency is considered a potential dependency until you validate it as permanent.

How Dependency Analysis Works

When you import data, Trillium automatically analyzes it for dependencies, identified as potential or discovered.

The following steps outline the process for examining and validating dependencies:

  1. Review potential dependencies discovered during the data import process.
  2. If any of these discovered dependencies are required and match the known data schema, verify them as permanent.
  3. If potential dependencies were not what you expected, re-run the dependency analysis and use different settings to expand the number of rows analyzed.

    For more information about analyzing dependencies, see Reasons to Analyze for Dependencies.