<div dir="ltr"><font face="Arial" style="color:rgb(0,0,0);font-size:12px">I will not do yet another </font><a href="http://openaccess.eprints.org/index.php?/archives/1150-Elsevier-updates-its-article-sharing-policies,-perspectives-and-services.html" style="font-family:Helvetica;font-size:12px">point-by-point rebuttal</a><font face="Arial" style="color:rgb(0,0,0);font-size:12px">, just to have it all once again ignored by Alicia/Elsevier, responding yet again with nothing but empty jargon and double talk: </font><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><font face="Arial"><br></font></div><blockquote style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;margin:0px 0px 0px 40px;border:none;padding:0px"><font face="Arial"><i>"At each stage of the publication process authors can share their research: before submission, from acceptance, upon publication, and post publication."</i></font></blockquote><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><div><font face="Arial"><br></font></div><div><font face="Arial">This “share” is a weasel word. It does not mean OA. It means what authors have always been able to do, without need of publisher permission: They can share copies — electronic or paper — with other individuals. That’s the 60-year old practice of mailing preprints and reprints individually to requesters. <b>OA means free immediate access online to all would-be users.</b></font></div><div><font face="Arial"><br></font></div></div><blockquote style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px;margin:0px 0px 0px 40px;border:none;padding:0px"><font face="Arial"><i>"For authors who want free immediate access to their articles, we continue to give all authors a choice to publish gold open access with a wide number of open access journals and over 1600 hybrid titles “</i></font></blockquote><div style="color:rgb(0,0,0);font-family:Helvetica;font-size:12px"><div><font face="Arial"><br></font></div><div><font face="Arial">In other words, now, the only Elsevier-autthorized way authors can provide OA is to pay extra for it (“Gold OA”).</font></div><div><font face="Arial"><br></font></div><div><font face="Arial">Since </font><a href="http://users.ecs.soton.ac.uk/harnad/Hypermail/Amsci/3771.html">2004</a><font face="Arial"> Elsevier had endorsed authors providing free immediate (un-embargoed) access (“Green OA”) by self-archiving in their institutional repositories. The double-talk began in </font><a href="http://openaccess.eprints.org/index.php?/archives/961-Some-Quaint-Elsevier-Tergiversation-on-Rights-Retention.html">2012</a><font face="Arial">.</font></div><div><font face="Arial"><br></font></div><div><font face="Arial">Elsevier can’t seem to bring itself to admit quite openly (sic) that they have (after a lot of ambiguous double-talk) back-pedalled and reneged on their prior policy, instead imposing embargoes of various lengths. They desperately want to be perceived as having taken a positive, progressive step forward. Hence all the denial and double-talk.</font></div><div><font face="Arial"><br></font></div><div><font face="Arial">They try to say that their decision is “fair” and “evidence based” — whereas in fact it is based on asking some biassed and ambiguous questions to some librarians, authors and administrators after having first used a maximum of ever-changing pseudo-legal gibberish to ensure that they can only respond with confusion to the confusion that Elsevier has sown.</font></div><div><font face="Arial"><br></font></div><div><font face="Arial">We cannot get Elsevier to adopt a fair, clear policy (along the lines of their original 2004 one) but we should certainly publicize as loudly and widely as possible the disgraceful and tendentious spin with which they are now trying to sell their unfair, unclear and exploitative back-pedalling.</font></div><div><font face="Arial"><br></font></div><div><font face="Arial">Stevan Harnad </font></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 21, 2015 at 12:05 PM, Wise, Alicia (ELS-OXF) <span dir="ltr"><<a href="mailto:A.Wise@elsevier.com" target="_blank">A.Wise@elsevier.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hello everyone –</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Just a quick note to draw your attention to our article, posted today in Elsevier Connect and in response to yesterday’s statement by COAR:
<a href="http://www.elsevier.com/connect/coar-recting-the-record" target="_blank">http://www.elsevier.com/connect/coar-recting-the-record</a><span style="color:#1f497d">.
</span><span style="color:black">I’ll also append the full text of this response below.</span></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">You might also be interested in this Library Connect webinar on some of the new institutional repository services we are piloting (<a href="http://libraryconnect.elsevier.com/articles/2015-01/webinar-institutional-research-repositories-characteristics-relationships-and-roles" target="_blank">http://libraryconnect.elsevier.com/articles/2015-01/webinar-institutional-research-repositories-characteristics-relationships-and-roles</a>)
and reading our policies for yourselves:</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<ul type="disc" style="margin-top:0in">
<li class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Sharing –
<a href="http://www.elsevier.com/about/policies/article-posting-policy" target="_blank">http://www.elsevier.com/about/policies/article-posting-policy</a></span></li><li class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Hosting -
<a href="http://www.elsevier.com/about/policies/hosting" target="_blank">http://www.elsevier.com/about/policies/hosting</a></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">With best wishes,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Alicia</span></p>
<p class="MsoNormal" style="margin-bottom:7.5pt;line-height:15.0pt;background:white">
<b><span style="font-size:13.5pt;font-family:"Arial","sans-serif";color:black">COAR-recting the record</span></b></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">We have received neutral-to-positive responses from research institutions and the wider research community. We
are therefore a little surprised that COAR has formed such a negative view, and chosen not to feedback their concerns directly to us. We would like to correct the misperceptions.
</span></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">Our sharing policy is more liberal in supporting the dissemination and use of research:
</span></p>
<ul type="disc">
<li style="color:black"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">At each stage of the publication process authors can share their research: before submission, from acceptance, upon publication, and post
publication. </span></li><li style="color:black"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">In institutional repositories, which no longer require a formal agreement to host full text content
</span></li><li style="color:black;line-height:15.0pt;background:white">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">Authors can also share on commercial platforms such as social collaboration networks
</span></li><li style="color:black;line-height:15.0pt;background:white">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">We provide new services to authors such as the share link which enables authors to post and share a customized link for 50 days free access to the final published article
</span></li><li style="color:black;line-height:15.0pt;background:white">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">For authors who want free immediate access to their articles, we continue to give all authors a choice to publish gold open access with a wide number of open access journals and over 1600 hybrid
titles </span></li></ul>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">Unlike the claims in this COAR document, the policy changes are based on feedback from our authors and institutional
partners, they are evidence-based, and they are in alignment with the STM article sharing principles. They introduce absolutely no changes in our embargo periods. And they are not intended to suddenly embargo and make inaccessible content currently available
to readers – as we have already communicated in </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="http://www.elsevier.com/connect/elsevier-updates-its-policies-perspectives-and-services-on-article-sharing" target="_blank"><span style="font-family:"Verdana","sans-serif"">Elsevier
Connect</span></a></span><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">.</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">In fact, we have been developing services, in partnership with libraries, to help institutional repositories track research output
and display content to their users. This includes:</span></p>
<p style="margin-left:.5in;text-autospace:none">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black"><span>•<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">Sharing metadata: In order to showcase an institutions’ work, an institutional repository must identify their institution’s research output. By integrating
the ScienceDirect metadata API into the repository, this task becomes simple. Even in cases where the repository doesn’t hold the full text manuscript, the article information and abstract can be displayed..</span></p>
<p style="margin-left:.5in;text-autospace:none">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black"><span>•<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">Sharing user access information and embedding final articles: We are testing a workflow in which a user’s access level to the full text is checked on the fly,
and if full text access is available, the user will be served the final published version, instead of the preprint or manuscript hosted by the repository. Users who are not entitled to view the full text of the final article will be led to the version available
in the repository, or- if this is not available- to a page where they can view the first page of the article and options for accessing it (including via interlibrary loan). This ensures that users will always be served the best available version. This also
enables the repository to display the best available version to their users even if no self-archived manuscript is available.</span></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">We have not only updated our policies, we are active in developing and delivering technology that enables research
to be shared more widely.</span></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">COAR states that the addition of a CC-BY-NC-ND license is unhelpful. Feedback suggests that clarity about how
manuscripts can be used is welcome, </span><span style="font-size:11.0pt;font-family:"Verdana","sans-serif"">when asked in surveys often choose NC ND of their own volition (see the T&F study from 2014 at
<a href="http://www.tandf.co.uk/journals/explore/open-access-survey-june2014.pdf" target="_blank">
http://www.tandf.co.uk/journals/explore/open-access-survey-june2014.pdf</a> ), and it works across a broad range of use cases.<span style="color:black"></span></span></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">Our refreshed policies are about green OA, and some elements of this – for example the use of embargo periods –
are specifically for green OA when it is operating in tandem with the subscription business model. Here time is needed for the subscription model to operate as libraries will understandably not subscribe if this material is available immediately and for free.
</span></p>
<p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size:11.0pt;font-family:"Verdana","sans-serif";color:black">In closing, we appreciate an open dialogue and are always happy to have a dialogue to discuss these, or any other,
issues further. </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#7f7f7f">Dr Alicia Wise</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#7f7f7f">Director of Access and Policy</span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#ff9900">Elsevier
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray">I The Boulevard I Langford Lane I Kidlington I Oxford I OX5 1GB</span><span style="font-family:"Arial","sans-serif";color:gray"></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray">M: <a href="tel:%2B44%20%280%29%207823%20536%20826" value="+447823536826" target="_blank">+44 (0) 7823 536 826</a> I E:
<a href="mailto:a.wise@elsevier.com" target="_blank">a.wise@elsevier.com</a></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray">Twitter: @wisealic</span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
</div>
<br>
<hr>
<p><span style="font-size:10pt;font-family:"Arial","sans-serif"">Elsevier Limited. Registered Office: The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084, Registered in England and Wales.</span>
<br clear="none">
</p>
</div>
</blockquote></div><br></div></div>