Starting from the end: What to do when restricted data is released

0Citations
Citations of this article
11Readers
Mendeley users who have this article in their library.

Abstract

Repository managers can never be one hundred percent sure of the security of hosted research data. Even assuming that human errors and technical faults will never happen, repositories can be subject to hacking attacks. Therefore, repositories accepting personal/sensitive data (or other forms of restricted data) should have workflows in place with defined procedures to be followed should things go wrong and restricted data is inappropriately released. In this paper we will report on our considerations and procedures when restricted data from our institution was inappropriately released.

References Powered by Scopus

Data sharing in genomics re-shaping scientific practice

258Citations
N/AReaders
Get full text

DSpace: An open source dynamic digital repository

189Citations
N/AReaders
Get full text

On making public policy with publicly available data: The case of U.S. communications policymaking

38Citations
N/AReaders
Get full text

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Cite

CITATION STYLE

APA

Teperek, M., Morgan, R., Ellefson, M., & Kingsley, D. (2017). Starting from the end: What to do when restricted data is released. Data Science Journal, 16. https://doi.org/10.5334/dsj-2017-010

Readers' Seniority

Tooltip

PhD / Post grad / Masters / Doc 3

75%

Researcher 1

25%

Readers' Discipline

Tooltip

Computer Science 2

33%

Social Sciences 2

33%

Engineering 1

17%

Agricultural and Biological Sciences 1

17%

Save time finding and organizing research with Mendeley

Sign up for free