> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/data-governance/data-discoverability.md).
# Data Discoverability
Data Discoverability in Astera’s Data Governance Platform
The previous [article](/astera-data-stack-v10/data-governance/modifying-asset-details.md) covered how data assets can be enriched in the platform.
Now, we’ll be looking into how those enrichments can assist with searching and filtering Data Assets in the Resource Catalog.
1. Navigate to the Resource Catalog page.
2. Use the Filter panel to specify the type, owner, deployed date, or tags to narrow down your search.
3. Click on *Apply Filter*. You will see the filters applied reflected on the resource catalog.
4. Next, search for the deployed data assets using the search bar. The searched term is matched against the name and description of the asset, and if found, the matched asset is returned in the results.
This concludes the searching and filtering of data assets in the resource catalog. In the next [article](/astera-data-stack-v10/data-governance/data-profile.md), we will look at how to generate the data profile for the above asset.
---
# 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://documentation.astera.com/astera-data-stack-v10/data-governance/data-discoverability.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.
