Publishing and Unpublishing Datasets

How to share (publishing) and stop sharing (unpublishing) with collaborators.

When you import a dataset, it is unpublished by default. You can choose to publish it to share with other collaborators that have the View Datasets and Data Schema policy set. To learn more, see Viewing Your Project's Permissions Policy. Also, if you have sensitive data, review the options you have for sharing that data before continuing. For more information, see Sensitive Datasets.

Publishing Datasets

To publish a dataset, complete the following steps.

1

Select publish from the three-dot menu.

2

A message appears asking if you would like to publish the dataset.

If you want to unpublish previously published versions of the dataset, leave the button for that option selected. Otherwise, deselect it.

3

Select the Publish Dataset button.

All other participants granted permission to view published datasets will be able to see the dataset. The Publish badge appears on the dataset entry in the Datasets screen.

Unpublishing a Dataset

To unpublish a dataset, complete the following steps.

1

Select unpublish dataset from the three-dot menu.

2

A message appears asking you if you want to unpublish the dataset.

3

Select Unpublish Dataset.

All other participants are no longer able to see the dataset.

Troubleshooting Publishing Issues

This section addresses common errors encountered when attempting to publish datasets or data schemas.

The "Publish" option is not on the menu

• Cause: The project's site-level permission for "View Datasets and Data Schemas" is likely set to Full Visibility(all of the personas have access to the dataset or data schema).

• Solution: In Full Visibility mode, all objects are shared with all project members by default; therefore, manual publishing is not required or available. To enable private drafting, a Project Lead must change the permission setting to Partial Visibility(only some of the personas have access to the dataset or data schema).

Error: "Cannot Publish Dataset" (Schema Ownership)

• The Issue: You are trying to publish a dataset, but the action is blocked.

• The Message: "The associated Data Schema version [Name] is currently unpublished and is owned by another workgroup."

• Why this happens: To ensure data integrity, a dataset cannot be public if its schema is private. Because the schema belongs to a different workgroup, you do not have the authority to publish it yourself.

• How to fix:

  1. Identify the owner of the Data Schema.

  2. Request that they Publish the specific schema version.

  3. Once the schema is published, retry publishing your dataset.

The Data Schema published automatically

• The Scenario: You published a dataset, and its associated schema status changed to "Published" without manual intervention.

• Explanation: If your workgroup owns both the dataset and the unpublished schema version, the Rhino FCP automatically publishes the schema to prevent broken dependencies.

• System Prompt: You should receive a confirmation dialog stating: "Publishing this dataset will automatically publish the associated Data Schema version. Do you wish to proceed?"

The Code Object or Dataset suddenly became "Unpublished"

• Cause: A user (likely a Data Custodian or Schema Owner) has Unpublished the underlying Data Schema.

• The Logic: Data Schemas are foundational. If a schema is pulled from public view, all "downstream" objects—such as Datasets that follow that schema or Code Objects that use it for input/output—are automatically unpublished to maintain privacy and system consistency.

• Solution: Republish the Data Schema to restore visibility to the associated datasets and code.