Trust score settings decide which test runs count toward the stored trust score, how coverage is scored, where each day starts, and which tables get a score at all. Set the defaults on Settings > Trust Scores > Settings, then override them for a data source, schema or table where you need to.
These settings apply to the stored trust score only. The KPI bar and the Test Execution Activity panel use the date range picked on the page; see Live Quality Scores in Projects and the Catalog.
Global settings
| Setting | Default | What it does |
|---|---|---|
| Allow customization of Trust Score Settings for individual Data Sources | Off | Lets users with the Manage Trust Scores permission override settings on data sources, schemas and tables |
| Look Back Period | 14 day(s) | How many days of test runs count toward the quality, coverage and trust scores |
| Time Zone | Where each day starts and ends when applying the look back period and dating each day's record | |
| New objects included by default | On | New schemas and tables get a trust score and count toward their parent's averages |
| Allow object level changes to inclusion/exclusion | On | Lets users with Manage Trust Scores include or exclude individual objects |
| Default Impact Rating for New Tables | 0 - Unknown | The impact rating, and so the target trust score, a newly cataloged table starts with. See Impact Ratings |
| Coverage Weighting | 100, 0, 0, 0, 0 | The coverage score earned for covering one, two, three, four and five or more quality dimensions |
Look Back Period
The calculation counts every run that started within this many days. The daily calculation covers the full days before the run day; a manual refresh covers today plus the days before it. With a 14-day period:
| Calculation | Run date | Runs counted |
|---|---|---|
| Daily schedule | 10 March, just after midnight | 24 February to 9 March |
| Manual refresh | 10 March, 3:00 PM | 25 February to 10 March, 3:00 PM |
A longer period makes the score steadier and slower to react. A shorter one reacts faster, but a table whose tests run weekly can drop to "no runs" between runs and show a trust score of 0. Set the period longer than the interval between your least frequent scheduled runs.
The look back period can be set globally and for a data source or schema, not for a table. The calculation uses the schema's value if it has one, then the data source's, then the global value.
Time Zone
Days start at midnight in this time zone. It affects which runs fall inside the look back period and the date each day's record is filed under. Set it to the time zone your teams work in, so "today" in Validatar matches "today" for them.
Coverage Weighting
The table has five rows, one per dimension count. Each row's Weight is added to the rows above it to give the Cumulative Coverage Score for that many dimensions. The weights must total 100%.
| Quality Dimension | Default weight | Default cumulative | Example weight | Example cumulative |
|---|---|---|---|---|
| 1st Dimension | 100% | 100% | 60% | 60% |
| 2nd Dimension | 0% | 100% | 20% | 80% |
| 3rd Dimension | 0% | 100% | 10% | 90% |
| 4th Dimension | 0% | 100% | 5% | 95% |
| 5th Dimension | 0% | 100% | 5% | 100% |
The rows are positions, not named dimensions. A table whose tests cover Completeness and Validity scores the same as one whose tests cover Uniqueness and Timeliness: both cover two dimensions. To reward particular dimensions, decide which tests every important table should have and set the weighting so that anything less falls short.
With the default weighting, one tested dimension earns full coverage, so the trust score equals the quality score on a five-star scale. Choose a stricter weighting, like the example, if you want trust scores to reflect breadth of testing as well as pass rate.
Coverage weighting can be overridden for a data source, schema or table. The calculation uses the most specific setting that exists: table, then schema, then data source, then global.
Overriding settings for a data source, schema or table
- Open the data source, schema or table in the Catalog.
- Open the menu beside the trust score stars at the top of the page and choose Trust Score Settings.
- Select Override default ... settings to break from the parent level, then change the values.
- Save.
To switch trust scores off for the object, clear Enable Trust Scores. An excluded table gets no score and drops out of its schema's and data source's averages after the next calculation. On a data source, the Overrides tab lists the schemas that have their own settings.
You need the Manage Trust Scores permission on the data source. If the global settings do not allow customization, the fields are read-only and show which level controls them.
When changes take effect
Setting changes apply from the next calculation. They do not rewrite earlier days in the trust score history. To see the effect today, use Refresh Trust Score on a table, or Refresh Trust Scores on a schema or data source.