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 and you must be an owner or contributor on the Project to which you want to mount the Dataset.

Launch Domino and open the Project that you want to work with.
From the left navigation pane, click Data > Datasets.
On the Domino Datasets page, click the Mount Shared Dataset button.
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.

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.

Unmount a shared Dataset

Unmounting a shared Dataset does not remove it from existing executions until the execution completes. However, the Dataset is not available for new executions in this Project. To unmount a Dataset, you’ll need the appropriate Dataset role and you must be an owner or contributor on the Project from which you want to unmount the Dataset.

Open the Project that you want to unmount the Dataset from.
From the left navigation pane, click Data > Datasets.
Look for the Dataset you want to unmount in the Domino Dataset list.
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:

File formats	File types
Microsoft Office	.doc, .docx, .ppt, .pptx, .xls, .xlsx
OpenDocument	.odg, .odp, .ods, .odt
Other	.csv, .pdf, .rtf, .xml
SAS	.sas7bdat

Choose which Datasets and snapshots to mount

By default, every Dataset attached to a Project mounts into your executions with all of its snapshots at their versioned paths (see Understand Dataset paths below). You can pin any one of them to a single snapshot instead, for the length of that execution. Do it on the Data Plane & Hardware tab when you launch a Workspace or Job, or when you define a scheduled Job. Domino lists each mounted Dataset and NetApp Volume there in a table with Storage and Snapshot columns, and the Snapshot column is where you pick. A pinned snapshot mounts read-only at the path the live Dataset normally uses, for example /domino/datasets/local/<name>, so your existing code paths keep working. Choose a snapshot per asset at launch covers every option, how long the selection lasts, and what changes about the asset’s other mounts.

Find a Dataset path to access it in your code

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: from the left navigation, click Workspaces > Settings.
- In a running Workspace: from the left navigation, click Data > Datasets.
From a Job:
- When launching a Job: 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:

/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:

/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 for data reproducibility.
Learn about Dataset best practices.

Core Concepts

Features

Use Datasets and snapshots

Mount a Dataset

Unmount a shared Dataset

Render a Dataset

Choose which Datasets and snapshots to mount

Find a Dataset path to access it in your code

Understand Dataset paths

Dataset paths in DFS projects

Dataset paths in Git-based projects

Next steps

​Mount a Dataset

​Unmount a shared Dataset

​Render a Dataset

​Choose which Datasets and snapshots to mount

​Find a Dataset path to access it in your code

​Understand Dataset paths

​Dataset paths in DFS projects

​Dataset paths in Git-based projects

​Next steps

Mount a Dataset

Unmount a shared Dataset

Render a Dataset

Choose which Datasets and snapshots to mount

Find a Dataset path to access it in your code

Understand Dataset paths

Dataset paths in DFS projects

Dataset paths in Git-based projects

Next steps