> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/maintaining-data/identifying-datasets-dependencies.md).

# Identifying datasets dependencies

Using dataset dependencies is a great way to:

* Understand the impact of an action on a dataset (edit, delete, duplicate...) on other datasets and visualizations
* Navigate between depending datasets
* Identify unused datasets (not tied to any visualizations) to clean them

To see dependencies on a dataset, check the dependency column within the dataset list in the DataHub, Dataset section.

<figure><img src="https://1809014303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxYYf1KpgarKMgMsDCrw%2Fuploads%2Fgit-blob-4f07641cff3724563fb666654598fd6996ffd6a5%2FDocumentation_DataHub_Dependencies.png?alt=media" alt="Dependency view with 4 icons" width="265"><figcaption><p>Dataset dependency area</p></figcaption></figure>

For a given dataset you will find the depending:

* Datasource(s): connector or files used by the dataset or a parent dataset
* Parent dataset(s): dataset(s) used to create this dataset or another parent dataset
* Child dataset(s): dataset(s) created on top this dataset or another child dataset
* Home or stories: home tiles or story charts using this dataset or a child dataset

<figure><img src="https://1809014303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxYYf1KpgarKMgMsDCrw%2Fuploads%2Fgit-blob-85d4366bbea8e57b59dab87fde84f3638fa12445%2FDocumentation_DataHub_Dependencies.jpg?alt=media" alt="Diagram representing dependencies with a dataset"><figcaption><p>Dependencies in Toucan</p></figcaption></figure>


---

# 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-v3.toucantoco.com/data-management-in-datahub/datasets-in-toucan/maintaining-data/identifying-datasets-dependencies.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.
