> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/core-concepts/findings/data-quality-monitors/patterns.md).

# Patterns

The Patterns monitor detects similarities between string values across columns and down-scores any uncommon observations.

The following table describes the information available on the Patterns tab of the Findings page.

<table><thead><tr><th width="152">Column</th><th>Description</th></tr></thead><tbody><tr><td><img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-5d5a447dce86ff44cb212f6fa822c736f80b3704%2FPlusIcon.svg?alt=media" alt="Plus icon" data-size="line"></td><td><p>A data preview of the actual value and the predicted value.</p><p>Click <img src="https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-5d5a447dce86ff44cb212f6fa822c736f80b3704%2FPlusIcon.svg?alt=media" alt="Plus icon" data-size="line"> to expand the observation. The first row in the data preview is the actual value and the second row is the predicted value.</p></td></tr><tr><td>Type</td><td>The type of pattern detected, for example, Suggestive.</td></tr><tr><td>Observation</td><td>An overview of the pattern observation. The format of this column is [actual value in columns where a pattern is detected -> predicted value in columns where a pattern is detected].</td></tr><tr><td>Count</td><td>The number of patterns detected in the column.</td></tr><tr><td>Status</td><td><p>Lets you <a href="/data-quality-self-hosted/core-concepts/findings/working-with-assignments.md">label and train</a> a finding. The available dropdown menu options are Validate, Invalidate, and Resolve.</p><p><strong>Validate</strong> instructs Collibra DQ to either assign a finding to a specific user for review, which then appears in the View the Assignment Queue or acknowledge without an assignee that the finding is a valid observation.</p><p><strong>Invalidate</strong> instructs Collibra DQ to ignore a finding and allow the value to pass. There are two invalidation options:</p><ul><li><strong>Save</strong> lets you mark a finding as invalidated.</li><li><strong>Save &#x26; Retrain</strong> lets you invalidate a finding and any previously saved invalidated findings, if any.</li></ul><div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>When you have many findings to invalidate, it may be best to use the Save option to invalidate them at the same time, once all findings are reviewed.</p></div><p><strong>Resolve</strong> Instructs Collibra DQ to mark the finding as an observation and prevents it from appearing in future runs. Resolving a finding does not immediately affect data quality scores.</p></td></tr><tr><td>Profile</td><td><p>The user account that is assigned to this pattern finding. When the Status is Assigned, a user profile displays in this column.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>When a pattern finding is unassigned, the profile column is empty.</p></div></td></tr></tbody></table>

### Adjusting the downscore value

You may find that the default downscore value of 1 does not meet your requirements. Click the input field to the upper-left of the findings table and enter any whole number next to **DownScore Value** to adjust the downscore value of the pattern observations that Collibra DQ detects.

### Exporting rule break records

There are two options to export the details of your rule break records as .xlsx files:

* **Export** generates an Excel file with the details from the drill-in.
* **Export with Details** generates an Excel file with the details from the drill-in and the data preview, when available.

## Retrain

Updates the DQ models used for automated data-quality checks. The Retrain process consumes current training data (and optionally labels/config), builds a new model or rule-set, validates it, and publishes a new version that will be used to score incoming data and compute DQ metrics. Use **Retrain** when data distributions change, new labels/ground truth are available, business rules change, or on a scheduled cadence to prevent model drift.
