> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/dataset-configure-redaction/textual-datasets-review-results/dataset-text-search.md).
# Searching for text values
{% hint style="info" %}
To enable dataset text search, self-hosted instances must configure a connection to a search provider. For more information, go to [Enabling dataset text search](/textual/textual-install-administer/configuring-textual/enable-and-configure-textual-features/config-textsearch.md).
{% endhint %}
The **Entities** **Catalog** lists the values that Textual detected in the dataset files.
The **Dataset search** allows you to search for specific values to determine whether Textual detected them and assigned the correct entity type.
You can also use the [Textual Agent](/textual/textual-agent/textual-agent-about.md) to ask whether the dataset includes specific values.
Dataset search page
## Starting a search
To start a search:
1. On the dataset details page, click **Dataset search**.
2. In the search field, provide the text to search for.
When the text matches a full word in a file, Textual displays the results.
Textual only searches for full words. For example, if you type "nu", it does not find the word "number". You must type the full word "number".
## Viewing the search results
The search results include a separate row for each found instance of the search text.
Results for a dataset text search
For each instance, the results include:
* The instance itself, with the immediate context. The context includes the few words before and after the search text.
* The assigned entity type, if Textual detected the search text as an entity. If it did not, then the entity type is **None**.
* The name of the file where the instance was found.
At the top of the list, Textual displays the approximate number of matches and number of files that contain matches.
Depending on the number of matches, the list might not initially include all of the results. If there are additional results, then the **Load more** link displays. When you click **Load more**, Textual adds the next batch of results to the end of the list.
## Filtering the search results
You can filter the results to only include matches in selected files.
To filter the results:
1. Click **Filter by file**.
2. In the file list, check the checkbox for each file to include the results for.
Filtering the dataset search results by file
---
# 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.tonic.ai/textual/dataset-configure-redaction/textual-datasets-review-results/dataset-text-search.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.
