Skip to content

Commit 17290f3

Browse files
authored
Update data_publication_or_destruction.md
1 parent 253ebf8 commit 17290f3

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

project-stages/evaluate/data_publication_or_destruction.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,13 @@
11
---
2-
layout: default
2+
layout: article
33
title: Data Publication or Destruction
44
date: 02/29/2024
55
author: Benjamin Kinsella, Rachel Wells
66
audience: DataKind Volunteers
77
category: project-stages
88
subcategory: evaluate
9+
previous: evaluation_report_and_sharing
10+
next: technical_project_close
911
---
1012

1113
At the end of every project, we need to make sure that we have a plan in place for appropriately taking care of the partner organization’s data. The decision for data publication or destruction should be made in partnership with the partner organization during the Design Stage, as part of the data management plan. Once the project is completed, review the policy selections and any wrap\-up steps in the [data management plan](/project-stages/design/data_storage_security_and_management_processes). Confirm the appropriate wrap\-up steps have been completed and update the data management plan to indicate who completed them and when. For more on responsible data destruction and retention, check out [The Engine Room's “Becoming RAD” resource](https://www.theengineroom.org/becoming-rad-new-resource-for-organisations-who-want-to-develop-plans-for-retention-archiving-and-disposal/).
@@ -20,4 +22,4 @@ If the expectation is to destroy the data, make sure to confirm with all the pro
2022
##### Data Publication
2123

2224

23-
If the decision is to publish the data, make sure that the final dataset is cleaned, checked, and properly labeled and formatted with a descriptive and clear data dictionary. Work closely with the Project Champion in reviewing the data and the associated data documentation before publication. Although this should already be the case, double check that there is no possible personally identifiable information or variables that can together substantially limit the number of people that a row might refer to to the point of potentially putting anyone’s personal information at risk. Confirm the dataset is ready and the plan is appropriate with all stakeholders at the partner organization and DataKind before publishing the data.
25+
If the decision is to publish the data, make sure that the final dataset is cleaned, checked, and properly labeled and formatted with a descriptive and clear data dictionary. Work closely with the Project Champion in reviewing the data and the associated data documentation before publication. Although this should already be the case, double check that there is no possible personally identifiable information or variables that can together substantially limit the number of people that a row might refer to to the point of potentially putting anyone’s personal information at risk. Confirm the dataset is ready and the plan is appropriate with all stakeholders at the partner organization and DataKind before publishing the data.

0 commit comments

Comments
 (0)