> For the complete documentation index, see [llms.txt](https://cleyrop.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cleyrop.gitbook.io/docs/documentation-fr-en/data-governance/catalogue.md).

# Catalog

The Catalog brings together **all published datasets** from projects and those created directly by Platform Managers.

It allows all authorized users to **explore** the available resources, to view their **metadata**, and to  **add them to their projects** according to their access rights.

***

## Origin of the catalog datasets

The datasets visible in the catalog come from two sources:

1. **Datasets created by Platform Managers**\
   To learn how to **create a dataset:** [from a data source](/docs/documentation-fr-en/data-and-ai-project/datasets/gerer-les-datasets.md#creer-un-dataset-depuis-un-import-local-1) or a [local import](/docs/documentation-fr-en/data-and-ai-project/datasets/gerer-les-datasets.md#creer-un-dataset-depuis-un-import-local)
   * These datasets are created directly in the catalog from a connected data source or an existing dataset.
   * They serve as **data reference repositories** across several projects.
   * Their management (update, deletion, publication) is exclusively the responsibility of **Platform Managers and identified owners**.
2. **Datasets published from a project**\
   To learn how to [**publish a dataset**](/docs/documentation-fr-en/data-and-ai-project/datasets/publier-au-catalogue.md)
   * The **project owner** can publish a dataset already available in their space to the catalog.
   * This publication makes the dataset visible to other users (depending on its sensitivity).
   * Once published, it remains synchronized with the original project for updates or refreshes.

## Explore the catalog

All Data Workers and Platform Managers can explore the catalog to view the available datasets. It is possible to filter datasets according to their metadata.

From a Dataset card in the catalog, you can access its detailed sheet for more information.

The display and available actions depend on the dataset's sensitivity level.

<table><thead><tr><th width="132.66015625">Sensitivity</th><th width="184.17578125">Visibility</th><th>Main actions</th></tr></thead><tbody><tr><td>Internal</td><td>Metadata, preview, refresh history</td><td>View details, view refreshes, preview, add to a project, export</td></tr><tr><td>Sensitive</td><td>Metadata only</td><td>View details, request access</td></tr><tr><td>Restricted</td><td>Metadata only</td><td>View details, request access</td></tr></tbody></table>

## Access rights and available actions

Available actions vary depending on:

* the type of dataset,
* the user's role,
* and the associated project permissions.

<table><thead><tr><th width="253.859375">Action</th><th>Comment</th></tr></thead><tbody><tr><td>Edit</td><td>Edit metadata (description, labels, scheduling, classification)</td></tr><tr><td>Delete</td><td>Removes the resource from the catalog and breaks project links.</td></tr><tr><td>Refresh</td><td>Reruns the extraction from the original data source.</td></tr><tr><td>Export</td><td>Export possible according to permissions (CSV).</td></tr><tr><td>Add to a project</td><td>Requires approval for sensitive or restricted datasets.</td></tr><tr><td>Subscribe to alerts</td><td>Available for all types of datasets.</td></tr></tbody></table>

## Subscribe to notifications

From the catalog page, users can subscribe to two types of notifications:

* **Refresh failure** of a dataset.
* **Data Quality rule** not met.

When an event occurs:

* an in-app notification appears in the notification center,
* a summary email is sent to all subscribers.

***

## Best practices

* Publish only datasets **that are validated and documented**.
* Use **descriptions and metadata** that are accurate to make searching easier.
* **Refresh** published datasets regularly to ensure data freshness.