You can add notes to a variety of objects including:
-
Baseline Analysis, Join, and Trillium Quality projects
-
Attributes
-
Entities
-
Permanent joins
-
Trillium Quality processes and output entities
For each note, you can define note classes and subclasses. There are different classifications of notes that are available out of the box, see table Default Note Classes and subclasses. You can also create custom classes and subclasses.
The note class and subclasses are useful in identifying the contents of a note and allows you to group notes together for reporting purposes.
Class |
Subclass |
Use this class to note |
---|---|---|
TS Quality |
||
|
To Do List |
List of items to attend to. |
|
Processing Details |
Detailed description of a Quality data process steps. |
|
Processing Results |
Results of a data quality process. You can save this information as either as a summary you have written and/or as copied data from List Views. |
|
Issues to Resolve |
Data issues and resolution requirements. |
Business |
||
|
Meaning |
Detailed description of the issue or data. |
Reconciliation |
||
|
Sum |
Expected sum for integer/decimal attributes. |
|
Record Count |
Expected record count for an entity. |
|
Data Volumes |
Data volume of an entity in a repository. |
Attribute |
||
|
Nulls |
Issue related to NULL values (blank fields) for an attribute. |
|
Ranges |
Issue related to the range of values for an attribute. |
|
Phonetic |
Issue with values that sound alike. For example, potential misspellings. |
|
Abnormal Values |
Issue related to value(s) with unexpected high or low frequency. |
|
Patterns |
Issue related to value(s) with unexpected pattern. |
|
Datatype |
Issues with unexpected data types. |
|
Technical Cleanse Rule |
Definition of the technical cleansing rules required or done for system reasons. |
|
Business Cleanse Rule |
Definition of the business cleansing rules required or done for system reasons. |
Mapping |
||
|
Mapped From |
Object from which an object is mapped. Mappings must be defined bi-directionally. |
|
Mapped To |
Object to which an object is mapped. Mappings must be defined bi-directionally. |
|
Out of Scope |
Object that is not considered in scope for mapping. |
|
Default Value |
Attribute that is not mapped from another attribute; in such cases, note the default value used. |
|
Error Processing |
Error processing rule that defines what to do if an error occurs. |
|
Complex Transformation |
Definition of complex data transformation rule. |
|
Medium Transformation |
Definition of medium data transformation rule. |
|
Simple Transformation |
Definition of simple data transformation rule. |
|
Select Criteria Rule |
Definition of how rows should be selected for extraction from the source. |
Join |
||
|
Outer Join Rule |
If an outer join is required for this join. |
|
Cardinality |
Definition of unexpected cardinality issue. |
|
Optionality |
Definition of unexpected optionality issue. |
|
RI Rule |
Definition of unexpected Referential Integrity (RI) issue. |
Key |
||
|
Business Meaning |
Business significance of a key |
|
Duplication Issue |
Data duplication issue. |
|
Technical Cleanse Rule |
Technical description of how to correct an issue |
|
Business Cleanse Rule |
Business description of how to correct an issue. |
Dependency |
||
|
Business Meaning |
Business significance of the dependency. |
|
Conflict Issue |
Description of conflicts. |
|
Technical Cleanse Issue |
Technical description of how to correct the issue. |
|
Business Cleanse Issue |
Business description of how to correct the issue. |