> 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.3/dashboards/data-literacy-dashboard.md).
# Data Literacy Dashboard
A Data Literacy Dashboard analyzes crawled and documented data monthly throughout the year. It tracks term creation usage and assigns them to data objects, revealing trends in term activity and distribution across domains.
**Key Metrics:**
* **Individually Obtained Knowledge Progress:** Stacked bar graphs display the cumulative count of data objects users have interacted with (tables, columns, reports, etc.), highlighting areas of data exploration. It distinguishes between the total crawled data count (depicted in red) and the documented data count (shown in green) across all databases. The documented count represents the number of data objects that include essential metadata information.
* **Term Creation and Usage:** A stacked bar chart tracks the total number of terms created and published monthly.
* **Term Application:** A bar chart shows the cumulative number of terms applied to data objects, revealing active term usage over time.
* **Domain-Specific Knowledge:** A pie chart showcases term distribution across domains within the application. Hovering over the chart reveals percentages and term counts per domain.
* **Security and Updates:**
* **Controlled Access:** Administrators can grant view-only access to the dashboard while retaining exclusive control over data refreshes.
* **Automatic Updates:** A refresh button triggers an advanced job to update all metrics, ensuring users always have the latest data insights.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release8.3/dashboards/data-literacy-dashboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
