Proposal Open Access

Plan I - Towards a sustainable research information infrastructure

Björn Brembs; Konrad Förstner; Michael Goedicke; Uwe Konrad; Klaus Wannemacher; Jürgen Kett

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="">
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Plan I, infrastructure, journals, publishers, research funding, funding agencies</subfield>
  <controlfield tag="005">20210127002715.0</controlfield>
  <controlfield tag="001">4468511</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">ZB MED – Information Centre for Life Sciences</subfield>
    <subfield code="0">(orcid)0000-0002-1481-2996</subfield>
    <subfield code="a">Konrad Förstner</subfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universität Düsseldorf</subfield>
    <subfield code="a">Michael Goedicke</subfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Helmholtz-Zentrum Dresden-Rossendorf</subfield>
    <subfield code="0">(orcid)0000-0001-8167-9411</subfield>
    <subfield code="a">Uwe Konrad</subfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">HIS-Institut für Hochschulentwicklung</subfield>
    <subfield code="0">(orcid)0000-0003-4810-3693</subfield>
    <subfield code="a">Klaus Wannemacher</subfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Deutsche Nationalbibliothek</subfield>
    <subfield code="0">(orcid)0000-0001-9421-1447</subfield>
    <subfield code="a">Jürgen Kett</subfield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">893532</subfield>
    <subfield code="z">md5:c6ef8f1baf57485d6690f26f3cae005f</subfield>
    <subfield code="u"></subfield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2021-01-21</subfield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o"></subfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Universität Regensburg</subfield>
    <subfield code="0">(orcid)0000-0001-7824-7650</subfield>
    <subfield code="a">Björn Brembs</subfield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Plan I - Towards a sustainable research information infrastructure</subfield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u"></subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2"></subfield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;Public institutions in many countries are required by law (&amp;quot;spending rules&amp;quot;) to initiate a bidding/tender process above a certain procurement threshold. Scholarly journals are exempt from these spending rules, because the content of each journal can only be obtained from a single publisher - the &amp;quot;single source procurement&amp;quot; exemption. One consequence of this publisher monopoly are prices ranging 10-20 fold above publishing costs [1], or difficult and drawn-out negotiations to achieve technically trivial improvements (such as, e.g., improved accessibility, &amp;#39;open access&amp;#39;). This &amp;quot;vendor lock-in&amp;quot; prevents marked-based price pressure and stifles innovation. Therefore, functionalities such as efficient citation linking, interactive data visualizations or interoperabilities with data and code have yet to be implemented in the scholarly literature despite sometimes decades of scientist demands. The European Commission (DG Competition) has also acknowledged this problem [2]. For future services, concerning research data and scientific source code there is still a possibility to prevent such a vendor lock-in, with all its detrimental consequences, but time is of the essence. In this document, we would like to elaborate on the problem and provide suggestions for solutions. We see our suggestions as alternatives to &amp;quot;&lt;a href=""&gt;Plan S&lt;/a&gt;&amp;rdquo; or &amp;ldquo;&lt;a href=""&gt;Plan U&lt;/a&gt;&amp;rdquo;, so we chose to name our suggestion &amp;quot;Plan I&amp;quot;, for infrastructure.&lt;/p&gt;</subfield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.4454639</subfield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.4468511</subfield>
    <subfield code="2">doi</subfield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">proposal</subfield>
All versions This version
Views 3,8771,777
Downloads 1,039399
Data volume 853.1 MB356.5 MB
Unique views 2,5671,042
Unique downloads 926363


Cite as