{"id":12601,"date":"2014-02-06T15:23:46","date_gmt":"2014-02-06T20:23:46","guid":{"rendered":"http:\/\/blogs.library.duke.edu\/scholcomm\/?p=12601"},"modified":"2014-02-06T17:51:00","modified_gmt":"2014-02-06T22:51:00","slug":"so-what-about-self-archiving","status":"publish","type":"post","link":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/","title":{"rendered":"So what about self-archiving?"},"content":{"rendered":"<p>There is a persistent problem with polemics.\u00a0 When writing to address someone else&#8217;s position with which one disagrees, it is easy to lose sight of the proverbial forest for the trees.<\/p>\n<p>In my previous two posts, I was addressing a misunderstand that I am afraid might lead authors to be less attentive and assertive about their publication contracts than they should be.\u00a0 The specific issue was whether or not it is feasible to maintain that a copyright is transferred only in a final version of a scholarly article, leaving copyright in earlier versions in the hands of the author.\u00a0 I argued that this was not the case, that the distinction between versions is a construct used by publishers that has little legal meaning, and that author rights that do persist in earlier versions, as they often do, are created by the specific terms of a copyright transfer agreement (i.e., they are creatures of a license).\u00a0 These points, which I believe are correct, prompted a number of people to get in touch with me, concerned about how these specific &#8220;trees&#8221; might impact the overall forest of self-archiving policies and practices.<\/p>\n<p>So now I want to make several points that all address one conclusion; this argument about the nature of a copyright transfer does not necessarily have any significant impact on what we do to enhance and encourage self-archiving on our campuses.\u00a0 Most of the practices I am aware of already take account of the argument I have been making, even if they are not explicit about it.<\/p>\n<p>On the LibLicense list today, Professor Steven Harnad, who is a pioneer in the movement to self-archive scholarly papers, <a href=\"http:\/\/listserv.crl.edu\/wa.exe?A2=ind1402&amp;L=LIBLICENSE-L&amp;F=&amp;S=&amp;P=17803\">posted a 10-point strategy<\/a> for accomplishing Green open access.\u00a0 Essentially, he points out that a significant number of publishers (his number is 60%) allow authors to self-archive their final submitted versions of their articles, and that those who have retained this right should exercise it.\u00a0 Elsevier is one such publisher, about which more later.\u00a0 Harnad argues that there are other strategies available for authors whose copyright transfer agreements do not allow self-archiving of even the final manuscript.\u00a0 One option is to deposit the manuscript in a repository but embargo access to it.\u00a0 At least that accomplishes preservation and access to the article metadata, and it facilitates fulfillment of individual requests for a copy.\u00a0 Another option is to deposit a pre-print (the version of the article before peer-review) in a pre-print repository, which is a solution that has long worked well in specific disciplines like physics and computer science.<\/p>\n<p>All of these strategies are completely consistent with the point I have been making about copyright transfer agreements.\u00a0 Harnad&#8217;s model recognizes that copyright is transferred (perhaps improvidently) to publishers, and is based on authors taking full advantage of the rights that are licensed back to them in that transaction.\u00a0 This makes perfect sense to me and nothing I have written in my previous two posts diminishes from this strategy.<\/p>\n<p>One of the questions I have received a couple of times involves campus open access policies and how they affect, or are affected by, copyright transfers.\u00a0 These policies often assert a license in scholarly articles, so the question is essentially whether that license survives a transfer of copyright.<\/p>\n<p>It is a basic principle of law, and common sense, that one cannot sell, or give away, more than one owns.\u00a0 So if an author has granted a license to her institution before she transfers her rights to a publisher, it seems clear that the license should survive, or, to put it another way, that the rights that are transferred to the publisher are still subject to this prior license.\u00a0 There was an <a href=\"http:\/\/papers.ssrn.com\/sol3\/papers.cfm?abstract_id=1890467\">excellent article written in 2012 by law professor Eric Priest <\/a>about this situation, and his conclusion is &#8220;that <span style=\"font-size: small\">permission mandates can create legally enforceable, durable nonexclusive licenses.<\/span>&#8221;\u00a0 The article provides an extensive analysis of the legal effect of this &#8220;Harvard-style&#8221; license, and is well worth being read in its entirety by all who are interested in the legal status of Green open access.<\/p>\n<p>An additional wrinkle to the status of a prior license is provided by section 205(e) of the copyright law, which actually addresses the issue of &#8220;priority between conflicting transfer of ownership and nonexclusive license.&#8221;\u00a0 This provision basically affirms what I have said above, that a license granted prior to a transfer of copyright survives the transfer and prevails over the rights now held by the transferee, IF it is evidenced by a written instrument.\u00a0 Because of this provision, some schools that have a license that is created by an open access policy also get a document from the author at the time of OA deposit that affirms the existence of that license.\u00a0 Such documentation helps ensure the survival of a policy-based license even after the copyright is later trnsferred to a publisher.<\/p>\n<p>Even when we decide that a license for Green open access exists and has survived a copyright transfer, however, we still have a policy decision to make about how aggressively to assert that license.\u00a0 Many institutional practices look to the terms of the copyright transfer and try to abide by the provisions found therein, usually relating to the version that can be used and when it can be made openly accessible.\u00a0 They do this, I think, to avoid creating an uncomfortable situation for the authors.\u00a0 Even if legally that license they granted would survive the transfer of rights, if a conflict with the publisher developed, the authors (whom we are, after all, trying to serve) would be in a difficult place.\u00a0 So my personal preference is to conform our practice to reasonable publisher policies about self-archiving and to work with authors to get unreasonable policies changed, rather than to provoke a dispute.\u00a0 But this is a policy matter for specific institutions.<\/p>\n<p>Finally, I want to say a couple of things specifically about Elsevier, since it was Elsevier&#8217;s take down notices directed against author self-archiving that began this series of discussions.<\/p>\n<p>Elsevier&#8217;s policies permit authors to self-archive the final manuscript version of an article but not the published version, and, as far as I know, all of its take down notices were directed against final published versions on institutional or commercial websites.\u00a0 So it is true that in my opinion, based on the analysis I have presented over the past week, that Elsevier is legally justified in this take down campaign.\u00a0 It may well be a stupid and self-defeating strategy &#8212; I think it is &#8212; but they have the legal right to pursue it.\u00a0 Authors, however, also have the legal right, based on Elsevier&#8217;s policies that are incorporated into their copyright transfer agreements, to post an earlier version of the articles &#8212; the final author&#8217;s manuscript(s) &#8212; in place of these final published versions.\u00a0 So I hope that every time a take down notice from Elsevier that is directed against the author of the work in question is received, the article that is taken down is replaced by a\u00a0 final manuscript version of the same content.<\/p>\n<p>As many know, Elsevier also has an foolish and offensive provision in its current copyright transfer agreement that says that authors are allowed to self-archive a final manuscript version of their article UNLESS there is an institutional mandate to do so.\u00a0 As I have said before, this &#8220;you may if you don&#8217;t have to but not if you must&#8221; approach is an unjustifiable interference with academic freedom, since it is an attempt to tie faculty rights to specific policies that the faculty themselves adopt to further their own institutional and academic missions.\u00a0 Elsevier should be ashamed to take this stance, and our institutions that value academic freedom should protest.\u00a0 But based on what has been said above, we can also see how futile this approach really is.\u00a0 If the institution has a policy-created license, that license probably survives the copyright transfer, as Eric Priest argues.\u00a0 In that case, the denial of a self-archiving right only in cases where a license exists is meaningless precisely because that license does exist; authors could self-archive based on the license and do not need the grant of rights that Elsevier is petulantly withholding.\u00a0 I said above that institutions should consider whether or not they want to provoke disputes by relying on the prior existence of a license to self-archive.\u00a0 Elsevier, however, seems to have decided to provoke exactly that dispute with this provision, and they are even more unwise to do so since it is likely to be a losing proposition for them.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There is a persistent problem with polemics.\u00a0 When writing to address someone else&#8217;s position with which one disagrees, it is easy to lose sight of the proverbial forest for the trees. In my previous two posts, I was addressing a misunderstand that I am afraid might lead authors to be less attentive and assertive about &hellip; <a href=\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">So what about self-archiving?<\/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,32,33,36],"tags":[],"class_list":["post-12601","post","type-post","status-publish","format-standard","hentry","category-authors-rights","category-licensing","category-open-access-and-institutional-repositories","category-scholarly-publishing"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.5 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>So what about self-archiving? - 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\/02\/06\/so-what-about-self-archiving\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"So what about self-archiving? - Scholarly Communications @ Duke\" \/>\n<meta property=\"og:description\" content=\"There is a persistent problem with polemics.\u00a0 When writing to address someone else&#8217;s position with which one disagrees, it is easy to lose sight of the proverbial forest for the trees. In my previous two posts, I was addressing a misunderstand that I am afraid might lead authors to be less attentive and assertive about &hellip; Continue reading So what about self-archiving? &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/\" \/>\n<meta property=\"og:site_name\" content=\"Scholarly Communications @ Duke\" \/>\n<meta property=\"article:published_time\" content=\"2014-02-06T20:23:46+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2014-02-06T22:51:00+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=\"7 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\\\/02\\\/06\\\/so-what-about-self-archiving\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/\"},\"author\":{\"name\":\"Kevin Smith, J.D.\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/#\\\/schema\\\/person\\\/efc9b8deb1a1e82626f11fd55a3ea759\"},\"headline\":\"So what about self-archiving?\",\"datePublished\":\"2014-02-06T20:23:46+00:00\",\"dateModified\":\"2014-02-06T22:51:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/\"},\"wordCount\":1435,\"commentCount\":3,\"articleSection\":[\"Authors' Rights\",\"Licensing\",\"Open Access and Institutional Repositories\",\"Scholarly Publishing\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/\",\"url\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/\",\"name\":\"So what about self-archiving? - Scholarly Communications @ Duke\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/#website\"},\"datePublished\":\"2014-02-06T20:23:46+00:00\",\"dateModified\":\"2014-02-06T22:51:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/#\\\/schema\\\/person\\\/efc9b8deb1a1e82626f11fd55a3ea759\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/2014\\\/02\\\/06\\\/so-what-about-self-archiving\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/blogs.library.duke.edu\\\/scholcomm\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"So what about self-archiving?\"}]},{\"@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:\\\/\\\/secure.gravatar.com\\\/avatar\\\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g\",\"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":"So what about self-archiving? - 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\/02\/06\/so-what-about-self-archiving\/","og_locale":"en_US","og_type":"article","og_title":"So what about self-archiving? - Scholarly Communications @ Duke","og_description":"There is a persistent problem with polemics.\u00a0 When writing to address someone else&#8217;s position with which one disagrees, it is easy to lose sight of the proverbial forest for the trees. In my previous two posts, I was addressing a misunderstand that I am afraid might lead authors to be less attentive and assertive about &hellip; Continue reading So what about self-archiving? &rarr;","og_url":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/","og_site_name":"Scholarly Communications @ Duke","article_published_time":"2014-02-06T20:23:46+00:00","article_modified_time":"2014-02-06T22:51:00+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":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/#article","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/"},"author":{"name":"Kevin Smith, J.D.","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759"},"headline":"So what about self-archiving?","datePublished":"2014-02-06T20:23:46+00:00","dateModified":"2014-02-06T22:51:00+00:00","mainEntityOfPage":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/"},"wordCount":1435,"commentCount":3,"articleSection":["Authors' Rights","Licensing","Open Access and Institutional Repositories","Scholarly Publishing"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/","url":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/","name":"So what about self-archiving? - Scholarly Communications @ Duke","isPartOf":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#website"},"datePublished":"2014-02-06T20:23:46+00:00","dateModified":"2014-02-06T22:51:00+00:00","author":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/#\/schema\/person\/efc9b8deb1a1e82626f11fd55a3ea759"},"breadcrumb":{"@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blogs.library.duke.edu\/scholcomm\/2014\/02\/06\/so-what-about-self-archiving\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blogs.library.duke.edu\/scholcomm\/"},{"@type":"ListItem","position":2,"name":"So what about self-archiving?"}]},{"@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:\/\/secure.gravatar.com\/avatar\/7e621549dfd2ef4eccb0dfbe0c710482c7829676bf7bbe97134fd95e1d5ebd8e?s=96&d=mm&r=g","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\/12601","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=12601"}],"version-history":[{"count":11,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts\/12601\/revisions"}],"predecessor-version":[{"id":12612,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/posts\/12601\/revisions\/12612"}],"wp:attachment":[{"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/media?parent=12601"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/categories?post=12601"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.library.duke.edu\/scholcomm\/wp-json\/wp\/v2\/tags?post=12601"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}