Skip to main content

Data Status

As an SSOT, what are my responsibilities in view of the Data Status Dashboard (DSD)?​

As the SSOT for a dataset, you have the following responsibilities:

  • Alert DataHive of any data issues if and when they are Detected. This helps us log a data issue with the Detected label.
  • Formally verify any data issues raised to you. This helps us log a data issue with the Verified by SSOT label.
  • Promptly resolve any data issues raised to you. This helps us log a data issue with the Resolved by SSOT label.
  • On our part as DataHive, we will be equally accountable for helping to identify, validate and confirm resolutions of data issues with your help.

As an SSOT, how should I raise any discrepancies found in the Data Status Dashboard (DSD)?​

The DSD's primary purpose is to provide visibility on data issues.

Therefore, to raise and resolve any discrepancies on the DSD, please contact DataHive separately over email at admin@datahive.gov.sg

We have provided convenient filters for you to quickly identify relevant issues.

For more details on usage, please refer to the Filters Page and this SSOT Guide for examples of usage.

As a DataHive User, what should I do if I find an issue with the data that I am subscribed to?​

Drop us an email at admin@datahive.gov.sg with the details and we will follow up accordingly.

As a DataHive User who subscribes to a dataset, how do I find out the issues that might affect my data?​

We have provided convenient filters for you to quickly identify relevant issues.

For more details on usage, please refer to the Filters Page and this DataHive User Guide for examples of usage.

Q: When should a resolved data issue be reopened?​

A previously resolved data issue should only be Reopened if it is due to a previously imperfect resolution of the data issue (same affected scope, subset of data affected).

In all other cases, a new, separate data status should be created.

Tenant Admins can work together with SSOTs to understand if reopening of a resolved data issue is necessary.