> For the complete documentation index, see [llms.txt](https://docs.editable.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editable.io/working-with-editable/explore-data.md).

# Explore data

This section covers the following options for exploring the data:

**Search and filter:** When dealing with a large volume of data, the search and filter options can help you find specific records/details. This section demonstrates how to find and filter the necessary data.

**Sort and re-order:** Standard sorting orders, such as ascending and descending, can be applied to both numerical and non-numerical columns to arrange the records in a systematic manner and analyze them. Columns can also be reordered. This section covers both.

**Show/Hide columns:** This section describes how to display or hide columns in a table, particularly one with too many columns.

**Pin columns:** This section explains how to pin and freeze columns in a table.


---

# 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.editable.io/working-with-editable/explore-data.md?ask=<question>&goal=<user_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.