Skip to main content

Un-publish Dataset

info

Only Tenant Admins can un-publish datasets. If the dataset to be un-published is requested in at least 1 active data request, an additional approval from a Tenant Manager is required.

warning

Once a dataset is un-published, access to it in active data requests is immediately revoked and cannot be recovered.

Please provide ample warning to the data requestors before un-publishing a dataset, as far as reasonably possible.

Use Cases of Dataset Un-publishing​

As a Tenant Admin, you may wish to un-publish your dataset in necessary scenarios. In the table below, scenarios marked with ✅ are necessary scenarios for un-publishing a dataset. For scenarios marked with ❌, un-publishing is unnecessary as the action can be applied directly to a published dataset.

ActionDataset Onboard Method
File UploadingSnowflake Private Listing / DataHive Ingestion
Delete uploaded files✅N.A.
Add new datafields❌❌
Reorder datafields✅❌
Remove datafields✅✅
Change table name✅✅
Change tokenisation Key/IVN.A.✅
Set a compulsory datafield to non-compulsory or vice verse✅✅
Set a non-identifier datafield as an identifier or vice versa✅✅
Change data format✅❌
Set a date field as a non-date field✅✅
Remove scope filtering✅✅
All other changes❌❌
warning

Please refrain from un-publishing a published dataset if you do not need to apply the above mentioned changes, as this will revoke data requests' access to the dataset. Changes not mentioned above can be applied directly to a published dataset.

Un-publish Datasets​

You need to be a Tenant Admin of the dataset to un-publish it.

To un-publish a dataset, in the "Manage datasets" page, click on the ellipsis icon associated with the dataset and then click "Un-publish dataset".

Unpublish

If there are no active data requests associated with the dataset, you may click "Un-publish" immediately.

Unpublish Without Reason

If there are active data requests associated with the dataset, you have to provide the reason for un-publishing in the textbox. Please be reminded that the reason will be visible to your Tenant Manager(s) and data requestors.

Unpublish With Reason

Approve or Reject Dataset Un-publishing​

You need to be a Tenant Manager to be able to approve / reject dataset un-publishing.

Please click on the name of the dataset with "Pending Un-publishing" status.

Dataset Name

The details of the un-publishing request are shown at the top of the page. Please review the request carefully, especially the number of active data request(s) and the reason for un-publishing. The reason will be shown on the data request page once the dataset is un-published.

After reviewing the details, please click either "Reject" or "Approve un-publishing" to resolve the un-publishing request.

Unpublish Request

Impacts of Un-publishing​

When a dataset is un-published:

  1. It can no longer be discovered or requested by DataHive users.
  2. Requestors can no longer discover or request any data product that required it (as part of the data product).
  3. Fulfilled data requests automatically lose access to it; requestors can no longer download its data but can still access any other datasets from the same request.
  4. Pending data requests will be automatically rejected if it was the only dataset requested.
  5. Scope change requests will be rejected if they affect the dataset's scope.
  6. Any Changelogs and Data Statuses associated with the dataset will be deleted.

Re-publish Datasets​

After the dataset is un-published, you may edit and publish the dataset in the same way described in Edit and Publish Dataset.

Once the dataset is published again, it will be treated as a new dataset with a new dataset ID, which means:

  1. The revoked access in data requests cannot be restored.
  2. The affected data product (if any) will remain undiscoverable.
  3. Previous changelogs and data statuses will remain deleted.