Managing Relationship Status - trillium_discovery - 17.1

Trillium Discovery Center

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
17.1
Language
English
Product name
Trillium Discovery
Title
Trillium Discovery Center
Topic type
How Do I
Overview
Configuration
Reference
Administration
Installation
First publish date
2008

Reviewing data relationships helps you better understand the structure of your data and allows you to make better informed decisions regarding your data quality and remediation projects. When you drill down to relationship analysis, each join, key, and dependency relationship has a status of either:

  • Discovered—found as a potential relationship but not yet reviewed for validity.
  • Permanent—reviewed and verified. These represent relationships you want to save for further use.

You can change the status of a relationship depending on your needs and the validity of the analysis.

Guidelines: Note the following guidelines when reviewing analysis and deciding on the status of each relationship.
  • Dependencies. A dependency is a many-to-one data relationship where one or more attributes determine the value of another attribute within a single data source. After data is imported into a repository, review the results by examining each potential (discovered) dependency and decide which status it should have. For example, set a dependency to permanent if it is a potential dependency and has been verified against the full data volume.
  • Keys. A key consists of one or more attributes that uniquely identify and associate data within a data source. After your data is imported into a repository, review the potential (discovered) keys and determine whether they are relevant to your data investigation. You could set to permanent a potential key that has been verified against the full data volume. Alternately, you could change the status of a key that is permanent, but should be discovered.
  • Joins. A join represents an intersection of identical or related data across two or more data sources. Review join analysis results and decide whether to change the status of a join. For example, set to permanent a discovered join that you want to keep for further relationship analysis. Or, maybe the join is on an attribute that can act as an alternative unique identifier and therefore might be useful when there are issues with keys or when you want to create cross application joins.

To review data relationship analysis and change status

  1. Open a single data source and click the Summary tab. Details about the data source display, including the Relationships table. This table shows the number of permanent and discovered keys, dependencies, and joins in the data source.
  2. To drill down from the table to see associated metadata, do one of the following:
    • Click a number link to open a tab showing associated permanent or discovered relationships. For joins, a Venn Diagram also opens displaying join analysis information for the first join on the Joins tab.
    • Click the Keys, Dependencies, and Joins column titles. A tab for each type of relationship opens showing metadata, including whether the relationship is discovered or permanent.

    If there are no relationships available, a zero (0) displays and the drill-downs are unavailable.

  3. Change the status of the relationships displayed on an open tab by selecting the rows you want to change and clicking Permanent or Discovered, depending on the relationship's current status. When you change a status on a tab showing only permanent or discovered joins, dependencies, or keys, that relationship is removed from the tab since its status has been changed. For joins, the Venn Diagram updates with the new status.
  4. Optional: Delete a relationship. See Deleting Relationships.