{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "chem-bla-ics",
  "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.",
  "home_page_url": "https://chem-bla-ics.linkedchemistry.info/",
  "feed_url": "https://chem-bla-ics.linkedchemistry.info/2024/11/23/version-of-record.json",
  "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png",
  "language": "en",
  "authors": [
    {
      "name": "Egon Willighagen",
      "url": "https://orcid.org/0000-0001-7542-0286",
      "_orcid": "0000-0001-7542-0286"
    }
  ],
  "items": [

    {
      "id": "https://doi.org/10.59350/9mb5c-y3a10",
      "url": "https://chem-bla-ics.linkedchemistry.info/2024/11/23/version-of-record.html",
      "title": "Version of record, and what Open Access must learn from Open Science",
      "content_html": "<p>Before we go into the learning bit, let’s just revisit what a <em>version of record</em> is. Wikipedia\n<a href=\"https://en.wikipedia.org/wiki/Version_of_record\">describes it</a> as\n“the fully copyedited, typeset and formatted copy of a manuscript as published” (with two references).\nBasically, in the whole scheme of research output, it is a <em>release</em>. It is a tagged version of the\noutput, allowing people to discuss that version specifically, so that we do not run into endless “oh, but\nI meant version <code class=\"language-plaintext highlighter-rouge\">manuscript_rewrite_V2_AE_MB_Fixed.docx</code>”. Really, publishing is not unique at all and\npublishers are doing it wrong.</p>\n\n<p>So, with “version of record” defined, why do we have only one in publishing?</p>\n\n<p>There is absolutely no reason not to have multiple versions of the same narrative, as long as they\nare clearly tagged. Open Science has been doing this for two decades, but publishers have been slacking.\nRetractions are updated versions of the same article, as are corrections, corrigendum, and errata.\nIt is not that publishers do not know how to do it. Hesitently, they are accepting that preprints\nexist, but publishers tend to frame that as inferior versions. There was a paper earlier this month\nthat looked into how much the versions are really different, and when I find it again, I will add the link.</p>\n\n<p>Of course, money, control, power likely have a role here. And historic reasons too, I guess. After all,\nwhen you have to print a journal issue and send them by horse carriage to universities around the\nworld, making updates is indeed not trivial.</p>\n\n<h2 id=\"twitter-or-x-or-mastodon-or-bluesky\">Twitter or X (or Mastodon or Bluesky)</h2>\n\n<p>But as an openscientist, I have the urge to keep research output relevant. We do this for data, we\ndo this for community standards, and we do this for research code. Routinely. Again, for decades.\nMust open access not learn from open science here?</p>\n\n<p>I <a href=\"https://mastodon.social/@egonw/113252951241453752\">asked that recently on Mastodon</a>.\nSpecifically, should the <em>Ten simple rules for getting started on Twitter as a scientist</em> article\n(doi:<a href=\"https://doi.org/10.1371/journal.pcbi.1007513\">10.1371/journal.pcbi.1007513</a>) not be updated?\nLooking at the number of scientific papers that discuss social media in scientific\ncommunication, ten tips sound to me to be timeless. And I was interested in why or why-not the paper\nshould be updated. Content-wise, a trivial update would be to update the name to X, which is the\nname of what was formerly known as Twitter. But then, updating the paper to replace Twitter\nby Bluesky or Mastodon would not be that much work either.</p>\n\n<p>The discussion brought up various aspects of this question (and hereby thanks to all who joined the\ndiscussion!). Is it worth it? Is it legal? Should it be an update, or just a new paper? Who\nshould do it? Do scholars have some responsibility to keep there research relevant? If I string-replace\nTwitter with X, how do I make clear who the original authors are, and what my role is? How do we\nget PLOS to point to the new version (surely not as corrigendum)? I do not have the answers.</p>\n\n<p>But I do see differences between different types of research output and that\nmakes these question an essential part of <a href=\"https://recognitionrewards.nl/\">Recognition and Rewards</a>.\nIf it some types of output have different rules, then we do not give all scholars the same\nchance of recognition. Of course, this is the current situation, and just reflects that academia\nstill has much to do to adopt Open Science.</p>\n\n<h4>References</h4>\n<div class=\"csl-bib-body\">\n    <div class=\"csl-entry\">Cheplygina, V., Hermans, F., Albers, C., Bielczyk, N., &#38; Smeets, I. (2020). Ten simple rules for getting started on Twitter as a scientist. <i>PLOS Computational Biology</i>, <i>16</i>(2), e1007513. https://doi.org/10.1371/journal.pcbi.1007513 <a href=\"https://doi.org/10.1371/JOURNAL.PCBI.1007513\">CrossRef</a> <a href=\"https://qlever.scholia.wiki/doi/10.1371/JOURNAL.PCBI.1007513\">Scholia</a></div>\n  </div>",
      "summary": "Before we go into the learning bit, let’s just revisit what a version of record is. Wikipedia describes it as “the fully copyedited, typeset and formatted copy of a manuscript as published” (with two references). Basically, in the whole scheme of research output, it is a release. It is a tagged version of the output, allowing people to discuss that version specifically, so that we do not run into endless “oh, but I meant version manuscript_rewrite_V2_AE_MB_Fixed.docx”. Really, publishing is not unique at all and publishers are doing it wrong.",
      
      "date_published": "2024-11-23T00:00:00+00:00",
      "date_modified": "2024-11-23T00:00:00+00:00",
      "tags": ["publishing","openaccess","openscience"],
      "_references": [
        
          
          
            { "url": "https://doi.org/10.1371/JOURNAL.PCBI.1007513", "doi": "10.1371/JOURNAL.PCBI.1007513"
             }
            
          
        ],
      
      
      
      
      
      
        "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ]
      
    }

  ]
}
