bioRxivScientific Communication & EducationPreprint
Starting from the end: what to do when restricted data is released
Marta TeperekiD, Rhys Morgan, Michelle EllefsoniD, Danny KingsleyiD
Abstract
Repository managers can never be one hundred percent sure of the security ofhosted 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 wewill report on our considerations and procedures when restricted data from ourinstitution was inappropriately released.
Reproducibility ledger
Nobody has reported trying to reproduce this paper yet. Did you replicate an experiment or run the code? Your report saves the next lab a week.
Sign in to file a reproducibility report.
Related papers
- A Data Citation Roadmap for Scholarly Data Repositories
- Discovering Data Access and Use Requirements Using the Data Tags Suite (DATS) Model
George Charles Alter, Alejandra N Gonzalez-Beltran, … Philippe Rocca‐Serra·GigaSciencePeer-reviewed·Feb 1, 2020
- Publishing descriptions of non-public clinical datasets: guidance for researchers, repositories, editors and funding organisations
Iain Hrynaszkiewicz, Varsha Khodiyar, … Susanna-Assunta Sansone·bioRxiv·Feb 1, 2016
- Cloud Bursting Galaxy: Federated Identity and Access Management
Vahid Jalili, Enis Afgan, … Jeremy Goecks·BioinformaticsPeer-reviewed·Jun 5, 2019
- Files removed following a technical error
bioRxiv·bioRxiv·Oct 17, 2019
- Using experimental data as a voucher for study pre-registration
Matan Mazor, Noam Mazor, Roy Mukamel·bioRxiv·Nov 6, 2017