> ## Documentation Index
> Fetch the complete documentation index at: https://docs.domino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Use datasets and snapshots

Domino Datasets provide easy-to-use, fast, and organized storage for files in the Domino platform. You can create different sets of data within a project and share them with your teammates.

If you mount a dataset, others can use it in their own projects. If someone shares their Datasets with you, you can also mount them for use in your own project.

## Mount a dataset

To mount a dataset, you’ll need the appropriate [Dataset role](/cloud/platform-capabilities/core-concepts/data/sharing-and-security/share-datasets#dataset-roles) and you must be [an owner or contributor](/cloud/platform-capabilities/core-concepts/projects/collaborate-on-projects) on the Project to which you want to mount the dataset.

1. Launch Domino and open the **Project** that you want to work with.

2. From the left navigation pane, click **Data** > **Datasets**.

3. On the **Domino Datasets** page, click the **Mount Shared Dataset** button.

4. Choose the dataset that you want to mount from the **Dataset Name** menu, then click **Mount Dataset**.

The dataset that you selected should now appear in the **Shared Datasets** list. You can find the directory path for that dataset under **Name**.

<Note>
  Datasets (both imported and standard) are mounted as read-write (RW) or read-only (RO) based on the role of the user running the execution.
</Note>

## Unmount a shared dataset

Unmounting a shared dataset will not remove it from existing executions until the execution completes. However, the dataset will not be available for new executions in this Project.

To unmount a dataset, you’ll need the appropriate [Dataset role](/cloud/platform-capabilities/core-concepts/data/sharing-and-security/share-datasets#dataset-roles) and you must be [an owner or contributor](/cloud/platform-capabilities/core-concepts/projects/collaborate-on-projects) on the Project from which you want to unmount the dataset.

1. Open the **Project** that you want to unmount the dataset from.

2. From the left navigation pane, click **Data** > **Datasets**.

3. Look for the dataset you want to unmount in the **Domino Dataset** list.

4. At the end of its row, click the three vertical dots and click **Unmount**.

## Render a dataset

Domino supports tabulated previews for a number of file formats to streamline your data analysis and workflows. This minimizes downloading files and artifacts from Domino, while keeping sensitive data inside the Domino platform.

As a prerequisite for viewing in a tabulated format, make sure that the **Define.xml** file and its associated **style sheet (.xsl file)** are in the same directory. There are a couple of ways to view these:

* From within a **Domino Dataset**: Double-click the **Define.xml** file to render it in a readable format.

* From within Domino artifacts:

  * View **Styled XML**: click **Show Rendered XML** to render it in a readable format.

These are the supported file types for rendering:

<table>
  <thead>
    <tr>
      <th>File formats</th>
      <th>File types</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td><p><strong>Microsoft Office</strong></p></td>
      <td><ul> <li><p>.doc, .docx, .ppt, .pptx, .xls, .xlsx</p></li> </ul></td>
    </tr>

    <tr>
      <td><p><strong>OpenDocument</strong></p></td>
      <td><ul> <li><p>.odg, .odp, .ods, .odt</p></li> </ul></td>
    </tr>

    <tr>
      <td><p><strong>Other</strong></p></td>
      <td><ul> <li><p>.csv, .pdf, .rtf, .xml</p></li> </ul></td>
    </tr>

    <tr>
      <td><p><strong>SAS</strong></p></td>
      <td><ul> <li><p>.sas7bdat</p></li> </ul></td>
    </tr>
  </tbody>
</table>

## Find a dataset path to access it in your code

In order to access a dataset or a snapshot in your code, you need to know its path.

There are several ways to find the path to a dataset or any of its snapshots in Domino.

* From a Workspace:

  * [Before launching a Workspace](/cloud/platform-capabilities/core-concepts/workspaces/launch-a-workspace): from the left navigation, click **Workspaces** > **Settings**.

  * In a [running Workspace](/cloud/platform-capabilities/core-concepts/workspaces/manage-workspaces): from the left navigation, click **Data** > **Datasets**.

* From a Job:

  * When [launching a Job](/cloud/platform-capabilities/core-concepts/jobs/create-and-run-jobs): from the left navigation, click **Jobs**, choose the job from the list, then click **Details** > **Data**.

  * In a running Job, click **Details** > **Data**.

## Understand dataset paths

Domino executions (workspaces, jobs, apps, and launchers) automatically make datasets and their associated snapshots from a Project available.

The following configuration demonstrates the conventions followed by a predefined path:

* Dataset called `clapton` (local to the project)

  * Snapshot 1 (tagged with `tag1`)

  * Snapshot 2 (not tagged)

* Dataset called `mingus` (local to project)

  * Snapshot 1 (tagged with `tag2`)

  * Snapshot 2 (not tagged)

* Dataset called `ella` (shared from another project)

  * Snapshot 1 (tagged with `tag3`)

  * Snapshot 2 (not tagged)

* Dataset called `davis` (shared from another project)

  * Snapshot 1 (tagged with `tag4`)

  * Snapshot 2 (not tagged)

### Dataset paths in DFS projects

The mounting paths in DFS projects behave according to the following scheme:

**Dataset in the project:**

* `/domino/datasets/local/<name>` - mounted as RW

* `/domino/datasets/local/snapshots/<name>/<tag>` - mounted as RO

* `/domino/datasets/local/snapshots/<name>/1` - mounted as RO

* `/domino/datasets/local/snapshots/<name>/2` - mounted as RO

**Dataset imported from a different project:**

* `/domino/datasets/<name>` - mounted as RO

* `/domino/datasets/snapshots/<name>/<tag>` - mounted as RO

* `/domino/datasets/snapshots/<name>/1` - mounted as RO

* `/domino/datasets/snapshots/<name>/2` - mounted as RO

For a Domino File System (DFS) project, datasets and snapshots are available in the following hierarchy:

```console theme={null}
/domino
   |--/datasets
      |--/local               <== Local datasets and snapshots
         |--/clapton          <== Read-write dataset for owner and editor, read-only for reader
         |--/mingus           <== Read-write dataset for owner and editor, read-only for reader
         |--/snapshots        <== Snapshot folder organized by dataset
            |--/clapton       <== Read-write for owner and editor, read-only for reader
               |--/tag1          <== Mounted under latest tag
               |--/1             <== Always mounted under the snapshot number
               |--/2
            |--/mingus
               |--/tag2
               |--/1
               |--/2
      |--/ella                <== Read-write shared dataset for owner and editor, Read-only for reader
      |--/davis               <== Read-write shared dataset for owner and editor, Read-only for reader
      |--/snapshots           <== Shared datasets snapshots organized by dataset
         |--/ella             <== Read-write for owner and editor, read-only for reader
            |--/tag3          <== Mounted under latest tag
            |--/1             <== Always mounted under the snapshot number
            |--/2
         |--/davis
            |--/tag4
            |--/1
            |--/2
```

### Dataset paths in Git-based projects

The mounting paths in Git-based projects behave according to the following scheme:

**Dataset in the project:**

* `/mnt/data/<name>` - mounted as RW

* `/mnt/data/snapshots/<name>/<tag>` - mounted as RO

* `/mnt/data/snapshots/<name>/1` - mounted as RO

* `/mnt/data/snapshots/<name>/2` - mounted as RO

**Dataset imported from a different project:**

* `/mnt/imported/data/<name>` - mounted as RO

* `/mnt/imported/data/snapshots/<name>/<tag>` - mounted as RO

* `/mnt/imported/data/snapshots/<name>/1` - mounted as RO

* `/mnt/imported/data/snapshots/<name>/2` - mounted as RO

For Git-based Projects, the datasets and snapshots are available in the following hierarchy:

```console theme={null}
/mnt
   |--/data                  <== Local datasets and snapshots
     |--/clapton             <== Read-write dataset for owner and editor, read-only for reader
     |--/mingus              <== Read-write dataset for owner and editor, read-only for reader
     |--/snapshots           <== Snapshot folder organized by dataset
        |--/clapton          <== Read-write for owner and editor, read-only for reader
           |--/tag1          <== Mounted under latest tag
           |--/1             <== Always mounted under the snapshot number
           |--/2
        |--/mingus
           |--/tag2
           |--/1
           |--/2
   |--/imported
     |--/data
        |--/ella             <== Read-write shared dataset for owner and editor, read-only for reader
        |--/davis            <== Read-write shared dataset for owner and editor, read-only for reader
        |--/snapshots        <== Shared dataset snapshots organized by dataset
           |--/ella          <== Read-write for owner and editor, read-only for reader
              |--/tag3       <== Mounted under latest tag
              |--/1          <== Always mounted under the snapshot number
              |--/2
           |--/davis
              |--/tag4
              |--/1
              |--/2
```

## Next steps

* [Create and manage Dataset Snapshots](/cloud/platform-capabilities/core-concepts/data/datasets/version-data-with-snapshots) for data reproducibility.

* Learn about [Dataset best practices](/cloud/platform-capabilities/core-concepts/data/datasets/local-data).