> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/askedgi/administration-and-governance/governance.md).

# Governance

This article explains how to identify, register, and remediate Legacy Data Quality Issues in askEdgi. It describes how approved data quality remediation rules are associated with datasets and applied within the workspace without modifying the source data.

## What is a Legacy Data Quality Issue? 

A Legacy Data Quality Issue is a known data quality problem that exists in historical data and cannot be easily corrected in the source system. These issues often result from changes in business rules, regulations, system migrations, or data standards over time. 

Instead of modifying the source data, organizations define approved remediation rules to correct the data during analysis.

**Example**

A product dataset contains the $ symbol for multiple currencies:

<div align="left"><img src="/files/JRZEpy3XklglvOuCB9xG" alt="" height="283" width="624"></div>

* US Dollar (USD)
* Australian Dollar (AUD)
* Singapore Dollar (SGD)
* Canadian Dollar (CAD)

Although the symbol is the same, each currency represents a different monetary value. This can lead to incorrect reporting, analysis, and business decisions.

### Registering a Legacy Data Quality Issue

Before users can clean data in askEdgi, the issue must be reviewed, approved, and registered as a Legacy Data Quality Issue.

#### Identify the Data Quality Issue

Data quality issues can be identified:

* Manually by users
* Through automated Data Quality Rules
* Through Data Quality Recipes

  <div align="left"><img src="/files/p65dfzpMi14okFvrQSDe" alt="" height="297" width="624"></div>

In this example, users identify that the OECountryCurrencies table uses the same $ symbol for multiple country currencies.

#### Create an Output Table

After identifying the issue, users create an output table containing the records that require remediation.

The output table captures the affected data and serves as the source for creating service requests.

<div align="left"><img src="/files/dRnymecQp7zetCfpiHke" alt="" height="297" width="624"></div>

#### Create a Data Quality Service Request

Navigate to the output table. Select the three dots (⋮) menu next to the output table, and select Configure Action.

Choose Create Data Quality Service Request.

<div align="left"><img src="/files/796ogUAttWbTBB3vyrMo" alt="" height="297" width="624"></div>

The Create Data Quality Service Request wizard opens.

{% hint style="info" %}
The Table Column Data Quality Issue template is mapped to the Take Action feature in askEdgi. For this functionality to work, Legacy Data Quality Status must be enabled in the template's properties.&#x20;
{% endhint %}

<div align="left"><img src="/files/p0TBOdiry1UgbLdLWLsF" alt="" height="288" width="624"></div>

If a custom template is used instead of Table Column Data Quality Issue, ensure that this property is enabled on the custom template.

#### Map Output Table Columns

Map the output table columns to the fields required to configure the Service Request. It includes Object Id, Object Type, Summary and Description.  After completing the mapping, save the configuration.

Execute the Service Request Job

When the configuration is submitted:

* The system creates a background job.
* A Job ID is generated for tracking.
* Service Requests are created for the identified records.

Users can monitor the job status using the generated Job ID.

<div align="left"><img src="/files/iwAaS0xgUZhFV1JBFZ7J" alt="" height="297" width="624"></div>

#### Review the Job Results

After the job completes successfully, the output table displays:

* Service Request Number
* Request Status
* Related issue details

Users can select the Service Request Number to open the Service Request page and review the request details.

#### Review and Approval

Data Owners, Data Stewards, or designated administrators review the Service Request and the proposed remediation.

For the OECountryCurrencies example:

**Issue**

Multiple currencies use the same $ symbol.

**Corrective Action**

Prefix all non-USD dollar ($) symbols with the first two characters of their ISO currency code.

If the issue cannot be corrected in the source system and requires an approved workaround, the Service Request is approved and marked as a Legacy Data Quality Issue.

<div align="left"><img src="/files/r3OXzK910lxvIwcP7Jh5" alt="" height="297" width="624"></div>

The approved Corrective Action becomes the cleanup context associated with the dataset.

#### Dataset is Registered as a Legacy Data Quality Issue

Once approved:

<div align="left"><img src="/files/ks75Vg0sBeBX8aNu5pkQ" alt="" height="297" width="624"></div>

* The dataset is associated with the approved remediation rule.
* The issue is registered as a Legacy Data Quality Issue.
* The remediation becomes available for use in askEdgi.

When users add the dataset to an askEdgi workspace, the system displays a Data Quality Debt indicator, showing that approved cleanup logic is available for the dataset.

### Data Cleanup

Data Cleanup allows users to apply approved remediation rules directly within the askEdgi workspace without modifying the source data.Data Cleanup allows users to apply approved remediation rules to datasets that contain legacy data quality issues directly within the askEdgi workspace when those issues cannot be corrected in the source system.

#### Add a Dataset to the Workspace

When a dataset is added to the askEdgi workspace, the system checks whether any approved Legacy Data Quality Issues exist for that dataset.\
If approved cleanup rules are available, askEdgi displays a Data Quality Debt indicator next to the dataset.

<div align="left"><img src="/files/L88iu2vMwe9xoSSn3Yni" alt="" height="283" width="624"></div>

#### Review the Cleanup Context

Select the Data Quality Debt indicator to view the available cleanup context.

<div align="left"><img src="/files/VtddyKcgV21UX0Sh6WIf" alt="" height="283" width="624"></div>

The cleanup context includes:&#x20;

* Context Cleanup Rule

Users can review the details before deciding whether to clean the data.

#### Execute Data Cleanup

Select Clean Data to apply the approved remediation logic.

<div align="left"><img src="/files/s65fBNrvGdyI6kl3ysYF" alt="" height="283" width="624"></div>

askEdgi creates a new thread and executes the cleanup process in the workspace.\
During execution:

* The approved remediation logic is applied to the dataset.
* Source data remains unchanged.
* A cleaned version of the dataset is generated.

#### Review the Results

After execution, the cleaned dataset becomes available in the workspace.

<div align="left"><img src="/files/hi241ScqDBhe5mrLdtMP" alt="" height="283" width="624"></div>

Users can:

* View the cleaned data
* Review the execution details
* View the generated code and logic used during cleanup
* Verify how the remediation was applied

Analyze the Cleaned Dataset

The cleaned dataset can be used for:

* Analysis in askEdgi
* Reporting and dashboards
* AI-driven insights
* Data exports

Since the cleanup is applied only within the workspace, the original source data is not modified.

#### Data Quality Debt Status Update

After the cleanup is executed successfully:

* The approved remediation logic is applied to the workspace dataset.
* A cleaned dataset is generated and becomes available for analysis.
* The Data Quality Debt indicator is removed from the dataset in the workspace, indicating that the approved cleanup has been applied.

  <div align="left"><img src="/files/Ezoj0p6IQMrLFILQXR9e" alt="" height="297" width="624"></div>

#### Viewing Cleanup Information

Users can select the cleaned dataset in the workspace to review information about the applied cleanup. A Note section is displayed, providing details such as:

<div align="left"><img src="/files/7Bj9FeNPrb8GC5Mu6nfI" alt="" height="297" width="624"></div>

#### Controlled Transformation

Cleanup results in a derived dataset:

* Used only within the workspace session
* Can be removed to revert to original data
* Does not affect source systems

#### Explainability and Governance

All cleanup actions are fully governed and transparent:

* Based only on approved context
* Clearly explains issue, logic, and remediation
* Fully auditable and traceable

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA USA


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/askedgi/administration-and-governance/governance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.