{"id":12586,"date":"2014-01-28T12:10:28","date_gmt":"2014-01-28T17:10:28","guid":{"rendered":"http:\/\/blogs.library.duke.edu\/scholcomm\/?p=12586"},"modified":"2014-01-28T12:11:01","modified_gmt":"2014-01-28T17:11:01","slug":"setting-the-record-straight-about-elsevier","status":"publish","type":"post","link":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/","title":{"rendered":"Setting the record straight about Elsevier"},"content":{"rendered":"<p>There has been a lot of attention given to the moves by publishing giant Elsevier to enforce its policy regarding authors&#8217; rights to post his or her article on a personal website or in an institutional repository.\u00a0 Since Elsevier began sending take down notices last fall, first to Academia.edu and then to individual universities, it has become well-known that authors are allowed, under their contracts with Elsevier, to post their &#8220;final submitted version,&#8221; which refers to the last version of the article, after peer-review, that is sent to the journal, but not the final published version with whatever copy-editing and formatting that the publisher has added.<\/p>\n<p>This is a difficult distinction for faculty authors to understand.\u00a0 My colleagues and I talk about it all the time with our faculty authors, but they persistently do not see much difference between the two versions, so they sometimes believe that there is little reason to observe the distinction.\u00a0 Publishers think (or at least say publicly) that they add a lot of value to submitted manuscripts, but a great many authors do not see it that way.<\/p>\n<p>Unfortunately, some of the attention that this new strategy from Elsevier has garnered has made the difficulty of explaining what is going on to faculty authors a little more difficult.\u00a0 This<a href=\"http:\/\/www.economist.com\/news\/science-and-technology\/21593408-publishing-giant-goes-after-authors-its-journals-papers-no-peeking\"> article from <em>The Economist<\/em> Called &#8220;No Peeking&#8230;&#8221;<\/a> is a case in point.\u00a0 The article correctly suggests that this is going to prove a self-defeating tactic for Elsevier, whose desperation to stem the movement toward open access often leads it into foolish decisions.\u00a0 <em>The Economist<\/em>, however,\u00a0 misstates the copyright law in its article in a way that will unfortunately reenforce a common misconception on campuses.<\/p>\n<p>Here are three sentences from <em>The Economist<\/em> article that embody the misconception I am concerned about:<\/p>\n<blockquote><p>Like journalists writing for a newspaper, academics submitting an article to a journal usually sign contracts which transfer copyright to the publisher&#8230;. As the University of California, Irvine, which was on the receiving end of some of the takedown notices, points out in advice to its staff, it is usually only the final version of an article, as it appears in a journal, that is covered by publisher\u2019s copyright. There is nothing to stop scientists making earlier versions available.<\/p><\/blockquote>\n<p>The problem with the first sentence is that academic authors are really not like journalists.\u00a0 Many journalists are full-time employees of their newspapers, so that their articles are owned by the newspaper from the start, as works made for hire.\u00a0 On the other hand, academic authors are not employees of publishers and their writings are not work for hire.\u00a0 Their rights (as well as those of some free-lance journalist) are entirely governed by the contracts they sign.\u00a0 The important implication of this is that academic authors have much more control over the rights they surrender and retain than do journalists; faculty members can simply refuse to transfer copyright (because they own it unless and until it is transferred in writing) or they can negotiate the exact terms of publication, transferring or licensing some rights and holding on to others.<\/p>\n<p>The bigger issue in this article, however, is in the second and third sentences quoted above, about how the copyright that is transferred to publishers only &#8220;covers&#8221; the final version of the article.\u00a0 This is a common misconception that is both wrong and dangerous.\u00a0 It is the same misconception that leads some people to believe that if they re-draw an illustration, chart or table from a copyrighted publication, they do not implicate copyright.\u00a0 But the truth is that a copyright includes any work that is derived from the copyrighted work and is &#8220;substantially similar.&#8221;\u00a0 When someone wants to use a figure from a published work, they may well be able to do so under fair use, but redrawing the figure, unless it is redrawn into something quite different (which would undermine the purpose), does not alter the copyright situation.<\/p>\n<p>When we turn to the issue of article versions, the situation is the same.\u00a0 Each version is a revision of the original, and the copyright is the same for all these derivatives.\u00a0 When copyright is transferred to a publisher, the rights in the entire set of versions, as derivatives of one another, are included in the transfer.\u00a0 Authors are not allowed to use their post-prints because the rights in that version are not covered in the transfer; they are allowed to use post-prints only because the right to do so, in specified situations, is licensed back to them as part of the publication agreement.<\/p>\n<p>Once a copyright transfer has been signed, all of the rights that the author may still have are because of specific contractual terms, which are usually contained in the transfer document itself.\u00a0 In short, these agreements usually give all of the rights under copyright to the publisher and then license back very small, carefully defined slivers of those rights back to the author.\u00a0 One of those slivers is often, but not always, the right to use a submitted version, or post-print, in carefully limited ways.\u00a0 For example, many publishers allow posting of the submitted version only on defined websites, usually a personal site or institutional repository.\u00a0 Often the contracts also allow posting of the submitted version only after some lapse of time.\u00a0 These restrictions would not make sense or be enforceable IF the author retained some kind of copyright in earlier versions, as <em>The Economist<\/em> implies.\u00a0 But they do not; they have only, and exactly, what the contract gives back to them.<\/p>\n<p>One important lesson to be gained from this correction of the language of<em> The Economist<\/em> article is that publication contracts are extremely important.\u00a0 They entirely determine what an author can do with his or her own work in the future.\u00a0 For many academics, signing such agreements is a very bad idea; they should be negotiated, either to make them licenses to publish, which allows the author to retain her copyright, or to be certain that the rights that are licensed back are broad enough and flexible enough to permit the future uses the author wants.\u00a0 Before the transfer, the author has a good deal of leverage to negotiate these agreements, but afterward she has very little.\u00a0 So it is vital to pay attention to the agreement itself and not rely on a false sense of security based on a misconception of how copyright works.<\/p>\n<p>Another point to learn from this situation is that the whole idea of article &#8220;versions&#8221; is artificial.\u00a0 It has been developed primarily by publishers in order to make a claim that they add substantial value to the final published version, which may or may not be true, depending on the article and the publisher.\u00a0 Another marketing advantage that publishers get from this fabricated distinction is the ability to claim that they support author rights and reuse of articles to promote better access, while still retaining the ability to slap down authors who use their own articles in ways the publishers have not pre-approved.\u00a0 As my colleague Will Cross has put it, &#8220;This versioning is a creation of publishers to reenforce the sense that they are following the academic &#8220;<a href=\"http:\/\/ecommons.cornell.edu\/bitstream\/1813\/2719\/1\/Research_Libraries_and_Fair_Use.pdf\">gentleman&#8217;s agreement<\/a>&#8221; that Elsevier has been breaking here.&#8221;<\/p>\n<p>[Hat tip to Will Cross and to Lisa Macklin of Emory, who discussed the implications of this particular mistake with me by e-mail and provided some ideas incorporated herein. Will qualified his statement quoted above by acknowledging that pre-prints, especially, have a longer history, but the use of these distinctions as contractual dividing lines is related to recent pressures on publishing.]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There has been a lot of attention given to the moves by publishing giant Elsevier to enforce its policy regarding authors&#8217; rights to post his or her article on a personal website or in an institutional repository.\u00a0 Since Elsevier began sending take down notices last fall, first to Academia.edu and then to individual universities, it &hellip; <a href=\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Setting the record straight about Elsevier<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":122,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,26,36],"tags":[],"class_list":["post-12586","post","type-post","status-publish","format-standard","hentry","category-authors-rights","category-copyright-issues-and-legislation","category-scholarly-publishing"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.1.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Setting the record straight about Elsevier - Scholarly Communications @ Duke<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Setting the record straight about Elsevier - Scholarly Communications @ Duke\" \/>\n<meta property=\"og:description\" content=\"There has been a lot of attention given to the moves by publishing giant Elsevier to enforce its policy regarding authors&#8217; rights to post his or her article on a personal website or in an institutional repository.\u00a0 Since Elsevier began sending take down notices last fall, first to Academia.edu and then to individual universities, it &hellip; Continue reading Setting the record straight about Elsevier &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\" \/>\n<meta property=\"og:site_name\" content=\"Scholarly Communications @ Duke\" \/>\n<meta property=\"article:published_time\" content=\"2014-01-28T17:10:28+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2014-01-28T17:11:01+00:00\" \/>\n<meta name=\"author\" content=\"Kevin Smith, J.D.\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@klsmith4906\" \/>\n<meta name=\"twitter:site\" content=\"@klsmith4906\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kevin Smith, J.D.\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\"},\"author\":{\"name\":\"Kevin Smith, J.D.\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759\"},\"headline\":\"Setting the record straight about Elsevier\",\"datePublished\":\"2014-01-28T17:10:28+00:00\",\"dateModified\":\"2014-01-28T17:11:01+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\"},\"wordCount\":1267,\"commentCount\":12,\"articleSection\":[\"Authors' Rights\",\"Copyright Issues and Legislation\",\"Scholarly Publishing\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\",\"url\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\",\"name\":\"Setting the record straight about Elsevier - Scholarly Communications @ Duke\",\"isPartOf\":{\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#website\"},\"datePublished\":\"2014-01-28T17:10:28+00:00\",\"dateModified\":\"2014-01-28T17:11:01+00:00\",\"author\":{\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759\"},\"breadcrumb\":{\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Setting the record straight about Elsevier\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#website\",\"url\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/\",\"name\":\"Scholarly Communications @ Duke\",\"description\":\"Discussions about the changing world of scholarly communications and copyright\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759\",\"name\":\"Kevin Smith, J.D.\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g\",\"caption\":\"Kevin Smith, J.D.\"},\"url\":\"https:\/\/blogs.library.duke.edu\/scholcomm\/author\/ksmithl2duke-edu\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Setting the record straight about Elsevier - Scholarly Communications @ Duke","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/","og_locale":"en_US","og_type":"article","og_title":"Setting the record straight about Elsevier - Scholarly Communications @ Duke","og_description":"There has been a lot of attention given to the moves by publishing giant Elsevier to enforce its policy regarding authors&#8217; rights to post his or her article on a personal website or in an institutional repository.\u00a0 Since Elsevier began sending take down notices last fall, first to Academia.edu and then to individual universities, it &hellip; Continue reading Setting the record straight about Elsevier &rarr;","og_url":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/","og_site_name":"Scholarly Communications @ Duke","article_published_time":"2014-01-28T17:10:28+00:00","article_modified_time":"2014-01-28T17:11:01+00:00","author":"Kevin Smith, J.D.","twitter_card":"summary_large_image","twitter_creator":"@klsmith4906","twitter_site":"@klsmith4906","twitter_misc":{"Written by":"Kevin Smith, J.D.","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#article","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/"},"author":{"name":"Kevin Smith, J.D.","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759"},"headline":"Setting the record straight about Elsevier","datePublished":"2014-01-28T17:10:28+00:00","dateModified":"2014-01-28T17:11:01+00:00","mainEntityOfPage":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/"},"wordCount":1267,"commentCount":12,"articleSection":["Authors' Rights","Copyright Issues and Legislation","Scholarly Publishing"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/","url":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/","name":"Setting the record straight about Elsevier - Scholarly Communications @ Duke","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#website"},"datePublished":"2014-01-28T17:10:28+00:00","dateModified":"2014-01-28T17:11:01+00:00","author":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759"},"breadcrumb":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/01\/28\/setting-the-record-straight-about-elsevier\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blogs.library.duke.edu\/scholcomm\/"},{"@type":"ListItem","position":2,"name":"Setting the record straight about Elsevier"}]},{"@type":"WebSite","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#website","url":"https:\/\/blogs.library.duke.edu\/scholcomm\/","name":"Scholarly Communications @ Duke","description":"Discussions about the changing world of scholarly communications and copyright","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blogs.library.duke.edu\/scholcomm\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759","name":"Kevin Smith, J.D.","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g","caption":"Kevin Smith, J.D."},"url":"https:\/\/blogs.library.duke.edu\/scholcomm\/author\/ksmithl2duke-edu\/"}]}},"_links":{"self":[{"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts\/12586","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/users\/122"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/comments?post=12586"}],"version-history":[{"count":11,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts\/12586\/revisions"}],"predecessor-version":[{"id":12597,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts\/12586\/revisions\/12597"}],"wp:attachment":[{"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/media?parent=12586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/categories?post=12586"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/tags?post=12586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}