Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


1. Selection

INSERT PARTNER ABBREVIATION selects the data they will share on the HDX platform, within the limitations set by the Terms of Service.

2. Preparation

INSERT PARTNER ABBREVIATION prepares the selected data for publication. This may include cleaning the data and putting it into one of the supported formats. HDX encourages INSERT PARTNER ABBREVIATION to add HXL tags to the data.

3. Transmission

The data can be uploaded directly to the HDX platform as a resource or through a link to a remote URL such as Google Drive or DropBox or an API.

4. Storage and hosting

Data that is uploaded to HDX is stored on a third party’s servers, which are currently hosted in the United States but may be moved to a different location in the future. Data shared through a URL link is stored in the cloud or servers belonging to INSERT PARTNER ABBREVIATION.

5. HDX data check (quality and sensitivity control and data freshness checks)

All data publicly or privately shared through HDX is reviewed by a Centre for Humanitarian Data team member to ensure it follows the Terms of Service. This initial check is always performed by a member of the Centre's Data Partnerships team (DPT). A dataset will immediately be deleted from the HDX platform in case the data is found to contain personally identifiable information or other data that the Data Partnership Team DPT member considered likely to be sensitive.

...

  • In any case, the Data Policy Officer (Jos) is notified - in case the Data Policy Officer (Jos) is not available, this notification will be forwarded to the Data Partnerships Team lead (Javier) and to the Centre Lead (Sarah).In case the potentially sensitive data is row-level survey data, Mike will also be notified. 
    These team members, together with the Data Partnership Team member, review and document the case. After internal discussion, the contributor of the dataset will be notified and invited to jointly discuss the issue and to determine next steps.

Further, a dataset will be made private by the Centre for Humanitarian Data team member and the contributor will be notified immediately in case the Data Partnerships Team members finds that:

● The dataset is found to contain gaps that render the quality of the dataset insufficient for use by a humanitarian audience, or;

● There are no resources (files or links) or broken links are found, or;

● The dataset contains data that is not relevant to a humanitarian audience, or;

● Data was not shared in one of the suggested formats.

After the dataset has been uploaded, the Centre for Humanitarian Data team will conduct regular checks to verify that data on the platform is being maintained. If the dataset is found to be out of date, the Centre for Humanitarian Data team will contact the contributor to suggest that the data be updated or that the dataset update frequency indication be changed. If metadata is found to be incorrect, the Centre for Humanitarian Data team will notify the contributor, after which the Centre for Humanitarian Data team might correct the metadata.

6. Retention and deletion

i) Data shared through HDX will be accessible until such a time when:

a. INSERT PARTNER ABBREVIATION delete the data by clicking “Delete dataset”, in which case the data is purged from the HDX database, or;

...

  • microdata, the following steps will be taken: 
    1. The DPT member on duty makes the dataset private and creates a ticket in the SDC for Microdata Log (this sheet)
    2. Nafi obtains a copy of the microdata
    3. Nafi notifies the organization and explains the SDC process, through this email template, and offers the organization the opportunity to download their data before it is deleted from the platform
    4. After Nafi and the organization have downloaded a copy, or after 24hrs pass, the data is deleted from HDX unless it is to be reasonably expected that the data in question does not pose any significant risk, given the contents and context of the dataset
    5. Nafi applies the risk assessment tool which is part of the SDCmicro package developed by the World Bank
    6. Nafi shares back the risk assessment with DPT and Policy
    7. The organization focal point and Nafi reach out to the organization to inform them about the established risk level and suggested next steps
    8. If needed, Nafi applies the SDC tool to the data concerned, and conducts another risk assessment and estimates information loss, results are shared with organization focal point and policy email address
    9. Next steps are decided in a call to do case review and recommendation with organization, focal point, Nafi, and ideally data policy
    10. If the data is re-published on HDX after SDC has been applied, Nafi suggests to the contributor how to flag this in the metadata
    11. Lessons learned are recorded in the SDC for Microdata Log (available here) by Nafi