> For the complete documentation index, see [llms.txt](https://help.aristotlemetadata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aristotlemetadata.com/creating-and-editing/how-to-link-quality-statement-to-an-indicator.md).
# How to link Quality statement to an Indicator?
A Data Quality Statement records any known issues that may be related to a data asset. A Data Quality Statement assesses data against seven key factors: Institutional Environment, Relevance, Timeliness, Accuracy, Coherence, Interpretability & Accessibility.
#### Steps to Go to "Indicator" from dashboard
1. Click on "Browse" under "Metadata" section.
2\. Scroll down to "Indicators". After click on it, you would be navigated to the metadata having all the indicators in the registry.
3\. You can search indicator by name as shown to link quality statement.
### How to add Quality Statement links to Indicators?
1. Click on "Actions" Tab. From the drop list, click on "Open item editor"
2\. In the Advanced editor, Click on the "components" tab.
3\. Scroll down to "Quality Statement tab" under "Components" Tab.
4\. You can search the quality Statement by its Name and ID in the Pop Up as shown.
5\. Click on after adding Quality Statement.
The quality statement is link to your indicator.
---
# 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://help.aristotlemetadata.com/creating-and-editing/how-to-link-quality-statement-to-an-indicator.md?ask=&goal=
```
`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.