Recommended versus certified repositories: Mind the gap

Sean Edward Husen, Zoë G. De Wilde, Anita De Waard, Helena Cousijn

Research output: Contribution to journalArticlepeer-review

2 Scopus citations

Abstract

Researchers are increasingly required to make research data publicly available in data repositories. Although several organisations propose criteria to recommend and evaluate the quality of data repositories, there is no consensus of what constitutes a good data repository. In this paper, we investigate, first, which data repositories are recommended by various stakeholders (publishers, funders, and community organizations) and second, which repositories are certified by a number of organisations. We then compare these two lists of repositories, and the criteria for recommendation and certification. We find that criteria used by organisations recommending and certifying repositories are similar, although the certification criteria are generally more detailed. We distil the lists of criteria into seven main categories: “Mission”, “Community/Recognition”, “Legal and Contractual Compliance”, “Access/Accessibility”, “Technical Structure/Interface”, “Retrievability” and “Preservation”. Although the criteria are similar, the lists of repositories that are recommended by the various agencies are very different. Out of all of the recommended repositories, less than 6% obtained certification. As certification is becoming more important, steps should be taken to decrease this gap between recommended and certified repositories, and ensure that certification standards become applicable, and applied, to the repositories which researchers are currently using.

Original languageEnglish
Article number42
JournalData Science Journal
Volume16
DOIs
StatePublished - Sep 4 2017

Keywords

  • Certification
  • Data fitness
  • Data management
  • Data quality
  • Data repositories

Fingerprint

Dive into the research topics of 'Recommended versus certified repositories: Mind the gap'. Together they form a unique fingerprint.

Cite this