{"id":440,"date":"2011-06-07T21:30:41","date_gmt":"2011-06-08T04:30:41","guid":{"rendered":"http:\/\/www.michaeleisen.org\/blog\/?p=440"},"modified":"2011-06-07T21:31:01","modified_gmt":"2011-06-08T04:31:01","slug":"announcing-the-batavia-open-genomic-data-licence","status":"publish","type":"post","link":"https:\/\/www.michaeleisen.org\/blog\/?p=440","title":{"rendered":"Announcing The Batavia Open Genomic Data Licence"},"content":{"rendered":"

Prepublication release of genomic and other large-scale biological datasets is incredibly value to the research community. For the last decade big genome sequencing centers – backed by the NIH and other funders – have followed a set of\u00a0principles<\/a> outlined at a January 2003 meeting in Ft. Lauderdale sponsored by The Wellcome Trust. This so called “Ft. Lauderdale Agreement”\u00a0outlined a set of \u201cresponsibilities\u201d for funders, data producers and data users. Significantly, it reserves for data producers the right to first publication of analysis of their data, discouraging precisely the kind of prepublication use of data it is supposed to be encouraging. In practice it has also given data producers the power to create enormous consortia to analyze data they produce, effectively giving them disproportionate credit for the work of large communities. It’s a horrible policy that has significantly squelched the development of a robust genome analysis community that is independent of the big sequencing centers.<\/p>\n

As my lab has started to produce more genome sequence data, I have pondered how best to release these data to the public. On the one hand, I don’t want to do anything like Ft. Lauderdale. I want to encourage people to use my data – without feeling any obligation to include me in their plans or publications, and placing no restrictions on when they can publish.<\/p>\n

However, I feel strongly that people taking advantage of the free and open release of scientific data should reciprocate by ensuring that publications arising from the use of these data also be free and open. Therefore, I have created a new agreement – which I will start using to release sequencing data from my lab. To reinforce the open sharing principles which this sharing represents, the license requires users to publish any work arising from the use of the data in open access journals \u2013 that is it requires that publications arising from the use of openly shared data be themselves openly shared.<\/p>\n

I decided to name the license\u00a0after the Batavia Seamount, a subsurface feature in the Indian Ocean that is antipodal to Ft. Lauderdale, FL, to reflect failures of the \u201cFt. Lauderdale Agreement\u201d for sharing of DNA sequence data that restricts users\u2019 rights to publish public sequence data and fails to lead to the open sharing of publications arising from these data.<\/p>\n

So here it is.<\/p>\n

<\/p>\n

Batavia Open Genomic Data Licence<\/strong><\/p>\n

Written by Michael Eisen, June 2011<\/p>\n

This license governs the sharing of research data. It facilitates the pre-publication release of data in a way that ensures data producers receive proper credit for their efforts, encourages the creative use of these data by third parties, and guarantees that publications arising from these data will be freely and openly available.<\/p>\n

Specifically, the license grants the right to use the data for any legal purpose provided:<\/p>\n