> 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/general-information.md).
# General Information
## Displaying dataset information
You can display the dataset information by opening any dataset and going to the **information** tab
### Name & description
In this tab you can edit the dataset name as well as the dataset description. Creating clear names and description are crucial for proper maintenance and scalability of the project. Gather up with your team and decide on a taxonomy to adopt
### Schema
The schema block allow you to manage primary keys but also to view the output of the schema with all primary keys an foreign keys.
Learn more on how to manage primary keys
{% content-ref url="/pages/bz626amj0hyeLu269TgV" %}
[Primary Keys](/data-management/workbench/understanding-datasets/primary-keys.md)
{% endcontent-ref %}
### Relationships
Learn more on how to manage relationships here:
{% content-ref url="/pages/GodocfwavwIvOVYU6pGD" %}
[Relationships](/data-management/workbench/understanding-datasets/relationships.md)
{% endcontent-ref %}
### Delete
You can delete a dataset by **hovering** it in the **View Selector** under **Model** and clicking on the **three dots** or by clicking on the delete button in the **information** tab.
{% hint style="info" %}
Be careful when deleting a model this might break explorations that are using is or models it has been referenced in.
{% endhint %}
{% hint style="warning" %}
You cannot delete datasets that are managed by Whaly (meaning datasets created by the third party sources) In order to delete those datasets stop syncing them in the source panel.
{% endhint %}
---
# 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/general-information.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.
