Dryad’s Commitment to the Principles of Open Scholarly Infrastructure

Researchers, institutions, funders, and publishers have relied on Dryad for over 10 years to support open data publishing. Throughout, we have taken our responsibility as open infrastructure seriously. As a small nonprofit working in a crowded and complicated scholarly communications landscape, it has been our honor to serve as an exemplar for what is possible when you remain committed to the mission and to building coalitions with like minded organizations in order to achieve success.  

Since our founding, members of our board and our team have been involved in constructing best practices for open infrastructure organizations like ours. One foundational set was published as the Principles of Open Scholarly Infrastructure. Since these principles were first published as a blog post in 2015, our team has worked closely with the original authors and additional collaborators to ensure Dryad aligns internal processes and external commitments to reflect these principles.   

Our work continues to evolve and these principles remain influential in how Dryad evaluates our success and assesses our impact.  We understand that transparency is key to maintaining the trust we have built with our broad community.  The burden is on us to continuously show how our organization is durable, our long-term business model is sustainable, and that our governance is truly open and transparent.  

Running open scholarly infrastructure is a journey that takes time and care. In order to formalize our commitment to these goals, the Dryad Board of Directors earlier this month unanimously voted to affirm that Dryad is committed to the Principles of Open Scholarly Infrastructure. We hope that, by committing to these principles, we can preemptively address fundamental questions about accountability and sustainability that are inevitably raised regarding our services.

So how does Dryad currently meet POSI?

The Principles of Open Scholarly Infrastructure (POSI) proposes three areas that an Open Infrastructure organization can address in order to garner the trust of the broader scholarly community: accountability (governance), funding (sustainability) and protection of community interests (insurance).

As we look at how Dryad currently maps to the principles, please keep in mind three things:

  1. Items marked something as green, that doesn’t mean we think we do this perfectly. It simply means that we have internal processes that focus on this commitment and we have evidence that these processes have thus-far been working.
  2. The fact that something is green does not mean that we will rest easy. We could regress. Our processes need to be able to detect and address regressions.
  3. Our commitments need to be balanced. So we don’t want to do something to turn something green if it has an irreversible impact on another commitment. 
  4. The implication of #3 above, is that it may take us some time to meet all of the commitments. But again, this is a journey. 
Dryad POSI

 

 

Sustainable, Open Source Alternatives Exist

Authors: Dryad (Tracy Teal, Daniella Lowenberg) & Zenodo (Tim Smith, Jose Benito Gonzales, Lars Holm Nielsen, Alex Ioannidis)

Crossposted at Zenodo

Recently, the 4TU.ResearchData team published a blog post on their decision to take a commercial route through their repository tender process. As allies in the community, we are glad to know they have found a path forward that fits their needs. Discussions and analyses about scholarly communications infrastructure are important to ensure we’re exploring all options of technical, community and governance structures. There are tradeoffs, challenges, and opportunities in each situation, and each organization needs to make its own decisions based on their own set of constraints. Specifically, organizations need to consider resourcing in thinking about a hosted solution or maintaining infrastructure themselves. 

In furthering this conversation, we want to respond to their post, with concerns about several statements that inaccurately represent the ecosystem and organizations who have long supported open source infrastructure for research data.  The blog’s central question is: “We need sustainable long-term open source alternatives, who will that be?” Our answer is that these infrastructure do exist and we aim to correct this messaging, shining light on those that have long served as these sustainable, open, alternatives. 

As the organizations identified in the post: Dryad and CERN’s Digital Repositories Team responsible for InvenioRDM and Zenodo, we feel that the authors have overlooked the strong communities and infrastructure built up in both of our Dryad and CERN worlds over the last decade. There was an implication in the post that the decision was made around features and capabilities, whereas it was the structure of the process that excluded non-commercial open source solutions. Both of our teams met, separately and briefly (a single 1-hour meeting), with the 4TU.ResearchData team in 2019. Our takeaways were similar: the tender process was not one in which we would be able to compete, so we did not continue conversations. The decision was not made because of features, pilot-phases, or other product judgements. Our organizations were not represented in the tender process because the framework of this organizational decision-making processes, specifically, the bureaucracy of the tender process, presented a number of challenges eliminating us from the competition. These same challenges, which are faced by other  nonprofits and government agencies, inherently favor commercial entities that are well-suited to go through the process.

Another implication in the post was that hosted solutions and open source software are mutually exclusive, which is not the case. Dryad is a hosted open-source community that institutions, publishers, and funders utilize. Additionally, many commercial entities run their technology on open source solutions (e.g., Haplo and TIND). It serves only to further discredit the success of open source infrastructure if we do not acknowledge the backbone role various systems play across the repository and open research space.

We appreciate that there is now broader support for community infrastructure like ours. IOI is an example of an organization in this space looking to support and synthesize infrastructure. As supporters of research from all aspects of the process – institutions, funders, publishers, etc, it is important that we continue to boost the open-source communities that researchers have owned and adopted for many years. Additionally, we need to consider barriers to participation in a selection process. We have to question: if processes like the tender exclude these solutions, is the tender process the best way to reach a decision for how institutions can best support their community and researchers? Instead of focusing on creating new infrastructure, or disregarding the existence of current supported infrastructure, we should be partnering to find ways to better the workflows and repositories in place to support open research. 

Sustainable, open source alternatives for open research infrastructure not only exist but also thrive. Processes that disfavour non-commercial platforms and communities will continue to feed this cycle of questioning the sustainability of our well-adopted and researcher-supported platforms and illogically promote belief that commercial solutions are more sustainable and well suited to meet researcher needs. Rather than masking these decisions with feature comparisons, not being fully transparent about the challenges and politics presented, we should adopt accessible processes that promote all options that can best meet open science goals, and not knock down the well supported ecosystem that exists along the way.
https://blog.datadryad.org/category/open-infrastructure/
blog.datadryad.org
crawl=CC-MAIN-2021-17
58878
application/http; msgtype=response
sha1:TQGKXKDFKDBFOI6WFG3NZWXEHJQSK45O
<urn:uuid:6fe3e38c-925f-4329-a802-6d3552cd7dcb>
2021-04-14T23:29:07Z
192.0.78.12
text/html
sha1:DWNQSGVVDKDYXI6LH6WOJA273HGIFMUZ
<urn:uuid:f15ad05f-a73a-47dd-8ced-0443af9e5747>
https://blog.datadryad.org/category/open-infrastructure/
response
<urn:uuid:a6711a40-98e4-456f-9bd1-aab300f43314>
isPartOf: CC-MAIN-2021-17
publisher: Common Crawl
description: Wide crawl of the web for April 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-247.ec2.internal
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/