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

# Understanding Datasets

## What is a dataset?

A dataset on Whaly represents any kind of data that is outputted by your warehouse and made available through the Whaly interface. Models are datasets, raw data imported from your warehouse or from a third party are also datasets. When a dataset is generated by a SQL or Flow query we call that a Model.

All datasets share common informations such as:

* A name and a description
* Primary keys
* Relationships to other datasets
* Drills definition

Models have specific capabilities such as:

* Materialization

In this section you'll learn how to configure a dataset. 

If you are looking to model data jump to

{% content-ref url="/pages/5yqmPu4c64fEQBDFI0tU" %}
[Model Data](/data-management/workbench/model-data.md)
{% endcontent-ref %}

If you are looking to import datasets either from Third Parties or from your own warehouse jump to

{% content-ref url="/pages/kC2H7hHKaNNjyFq3RJVw" %}
[Import raw data](/data-management/workbench/import-raw-data.md)
{% endcontent-ref %}


---

# 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.whaly.io/data-management/workbench/understanding-datasets.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.