<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="" style="text-align: justify;"><font face="Arial" class=""><span style="font-size: 14px; line-height: 19px;" class="">(sorry for any cross-posting)</span></font></div><div class=""><span class="" style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;"><br class=""></span></div><div class=""><span class="" style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;">In its recently released “Sharing and Hosting Policy FAQ”, Elsevier “recognize(s) that authors want to share and promote their work and increasingly need to comply with their funding body and institution's open access policies.” However there are several aspects of their new policy that severely limit sharing and open access, in particular the lengthy embargo periods imposed in most journals- </span><span class="" style="font-size: 14px; font-family: Arial; line-height: 1.38; text-align: justify; vertical-align: baseline;">with about <a href="http://www.elsevier.com/__data/assets/pdf_file/0018/121293/external-embargo-list.pdf" class="">90% of Elsevier journals</a> having embargo periods of 12 months or greater. This is a significant rollback from the original 2004 Elsevier policy which required no embargos for making author’s accepted manuscripts available; and even with the 2012 policy change requiring embargoes only when authors were subject to an OA mandate.</span></div><div class=""><font face="Arial" class="" style="font-size: 14px;"><br class=""></font><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; text-align: justify;"><font face="Arial" class="" style="font-size: 14px;"><span class="" style="vertical-align: baseline;">With article processing charges (APCs) <font class="">that can cost as much as </font></span><span class="" style="vertical-align: baseline;"><font class=""><a href="https://www.elsevier.com/journal-authors/open-access/sponsored-articles" class=""><span class="" style="vertical-align: baseline;"><font class="" color="#0042aa">$5000 US dollars</font></span></a> </font>for publishing in one of Elsevier’s gold open access titles or hybrid journals, this is not a viable option for many researchers around the world. Furthermore, the rationale for lengthy embargo periods is to protect Elsevier’s subscription revenue. We do not believe that scientific, economic and social progress should be hindered in order to protect commercial interests. In addition, t</span><span class="" style="line-height: 1.38;">here is currently no evidence that articles made available through OA repositories will lead to cancellations.</span><span class="" style="line-height: 1.38;"> </span></font></div><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; text-align: justify;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class=""><br class=""></font></span></div><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; text-align: justify;"><font face="Arial" class="" style="font-size: 14px;"><span class="" style="vertical-align: baseline;">Elsevier’s new policy also requires that accepted manuscripts posted in open access repositories bear a CC-BY-NC-ND license. This type of license severely limits the re-use potential of publicly funded research. ND restricts the use of derivatives, yet derivative use is </span><a href="http://oaspa.org/why-cc-by/" class="" style="line-height: 1.38; text-decoration: none;"><span class="" style="color: rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline;">fundamental</span></a><span class="" style="vertical-align: baseline;"> to the way in which scholarly research builds on previous findings, for example by re-using a part of an article (with attribution) in educational material. Similarly, this license restricts commercial re-use greatly </span><a href="http://www.kuro5hin.org/story/2005/9/11/16331/0655" class="" style="line-height: 1.38; text-decoration: none;"><span class="" style="color: rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline;">inhibiting</span></a><span class="" style="vertical-align: baseline;"> the potential impact of the results of research.</span></font></div></div></div><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><font face="Arial" class="" style="font-size: 14px;"><br class=""></font><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt; text-align: justify;"><font face="Arial" class="" style="font-size: 14px;"><span class="" style="vertical-align: baseline;">Elsevier’s Director of Access & Policy, Alicia Wise states that they “have received neutral-to-positive responses from research institutions and the wider research community.” Yet, since the “</span><a href="https://www.coar-repositories.org/activities/advocacy-leadership/petition-against-elseviers-sharing-policy/" class="" style="text-decoration: none;"><span class="" style="color: rgb(17, 85, 204); text-decoration: underline; vertical-align: baseline;">Statement against Elsevier’s sharing policy</span></a><span class="" style="vertical-align: baseline;">” was published just one week ago (on Wednesday May 20, 2015), it has been signed by close to 700 organizations and individuals, demonstrating that there is significant opposition to the policy.</span></font></div><font face="Arial" class="" style="font-size: 14px;"><br class=""></font><p dir="ltr" class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 10pt;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class="">Elsevier has indicated that they “are always happy to have a dialogue to discuss these, or any other, issues further.” We would like to offer the following concrete recommendations to Elsevier to improve their policy:</font></span></p><ol class="" style="margin-top: 0pt; margin-bottom: 0pt;"><li dir="ltr" class="" style="list-style-type: decimal; vertical-align: baseline;"><p dir="ltr" class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 10pt;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class="">Elsevier should allow all authors to make their “author’s accepted manuscript” openly available immediately upon acceptance through an OA repository or other <font class="">open access</font> platform.</font></span></p></li><li dir="ltr" class="" style="list-style-type: decimal; vertical-align: baseline;"><p dir="ltr" class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 10pt;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class="">Elsevier should allow authors to choose the type of open license (from CC-BY to other more restrictive licenses like the CC-BY-NC-ND) they want to attach to the content that they are depositing into an open access platform.</font></span></p></li><li dir="ltr" class="" style="list-style-type: decimal; vertical-align: baseline;"><p dir="ltr" class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 10pt;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class="">Elsevier should not attempt to dictate author’s practices around individual sharing of articles. Individual sharing of journal articles is already a scholarly norm and is protected by fair use and other copyright exceptions. Elsevier cannot, and should not, dictate practices around individual sharing of articles.</font></span></p></li></ol><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><font face="Arial" class="" style="font-size: 14px;"><span class="" style="vertical-align: baseline;">We strongly encourage Elsevier to revise their policy in order to better align with the interests of the research community. </span>We would also be pleased to meet to discuss these recommendations with Elsevier at any time.</font></div><font face="Arial" class="" style="font-size: 14px;"><br class=""><br class=""></font><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span class="" style="vertical-align: baseline; font-size: 14px;"><font face="Arial" class="">Kathleen Shearer, Executive Director, COAR</font></span></div><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span class="" style="line-height: 1.38; font-size: 14px;"><font face="Arial" class=""><br class=""></font></span></div><div class="" style="line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;"><span class="" style="line-height: 1.38; font-size: 14px;"><font face="Arial" class="">Heather Joseph, Executive Director, SPARC</font></span></div></div></div></div><div><br class=""></div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, May 21, 2015 at 12:05 PM, Wise, Alicia (ELS-OXF) <span dir="ltr" class=""><<a href="mailto:A.Wise@elsevier.com" target="_blank" class="">A.Wise@elsevier.com</a>></span> wrote:<br class=""><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" class="">
<div class=""><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">Hello everyone –</span></p><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">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" class="">http://www.elsevier.com/connect/coar-recting-the-record</a><span style="color:#1f497d" class="">.
</span><span style="" class="">I’ll also append the full text of this response below.</span></span></p><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">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" class="">http://libraryconnect.elsevier.com/articles/2015-01/webinar-institutional-research-repositories-characteristics-relationships-and-roles</a>)
and reading our policies for yourselves:</span></p><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class=""> </span><br class="webkit-block-placeholder"></div>
<ul type="disc" style="margin-top:0in" class="">
<li class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">Sharing –
<a href="http://www.elsevier.com/about/policies/article-posting-policy" target="_blank" class="">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"" class="">Hosting -
<a href="http://www.elsevier.com/about/policies/hosting" target="_blank" class="">http://www.elsevier.com/about/policies/hosting</a></span></li></ul><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class=""> </span><br class="webkit-block-placeholder"></div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">With best wishes,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class="">Alicia</span></p><p class="MsoNormal" style="margin-bottom:7.5pt;line-height:15.0pt;background:white">
<b class=""><span style="font-size: 13.5pt; font-family: Arial, sans-serif;" class="">COAR-recting the record</span></b></p><p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">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: 11pt; font-family: Verdana, sans-serif;" class="">Our sharing policy is more liberal in supporting the dissemination and use of research:
</span></p>
<ul type="disc" class="">
<li style="" class=""><span style="font-size:11.0pt;font-family:"Verdana","sans-serif"" class="">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="" class=""><span style="font-size:11.0pt;font-family:"Verdana","sans-serif"" class="">In institutional repositories, which no longer require a formal agreement to host full text content
</span></li><li style="line-height: 15pt; background-color: white; background-position: initial initial; background-repeat: initial initial;" class="">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"" class="">Authors can also share on commercial platforms such as social collaboration networks
</span></li><li style="line-height: 15pt; background-color: white; background-position: initial initial; background-repeat: initial initial;" class="">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"" class="">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="line-height: 15pt; background-color: white; background-position: initial initial; background-repeat: initial initial;" class="">
<span style="font-size:11.0pt;font-family:"Verdana","sans-serif"" class="">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: 11pt; font-family: Verdana, sans-serif;" class="">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"" class=""><a href="http://www.elsevier.com/connect/elsevier-updates-its-policies-perspectives-and-services-on-article-sharing" target="_blank" class=""><span style="font-family:"Verdana","sans-serif"" class="">Elsevier
Connect</span></a></span><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">.</span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">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" class="">
<span style="font-size: 11pt; font-family: Verdana, sans-serif;" class=""><span class="">•<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">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" class="">
<span style="font-size: 11pt; font-family: Verdana, sans-serif;" class=""><span class="">•<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">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: 11pt; font-family: Verdana, sans-serif;" class="">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: 11pt; font-family: Verdana, sans-serif;" class="">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"" class="">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" class="">
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="" class=""></span></span></p><p class="MsoNormal" style="line-height:15.0pt;background:white"><span style="font-size: 11pt; font-family: Verdana, sans-serif;" class="">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: 11pt; font-family: Verdana, sans-serif;" class="">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" class="">Dr Alicia Wise</span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#7f7f7f" class="">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" class="">Elsevier
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray" class="">I The Boulevard I Langford Lane I Kidlington I Oxford I OX5 1GB</span><span style="font-family:"Arial","sans-serif";color:gray" class=""></span></p><p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray" class="">M: <a href="tel:%2B44%20%280%29%207823%20536%20826" value="+447823536826" target="_blank" class="">+44 (0) 7823 536 826</a> I E:
<a href="mailto:a.wise@elsevier.com" target="_blank" class="">a.wise@elsevier.com</a></span></p><p class="MsoNormal" style="text-autospace:none"><b class=""><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:gray" class="">Twitter: @wisealic</span></b></p><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"" class=""> </span><br class="webkit-block-placeholder"></div><div class=""><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d" class=""> </span><br class="webkit-block-placeholder"></div>
</div>
<br class="">
<hr class=""><p class=""><span style="font-size:10pt;font-family:"Arial","sans-serif"" class="">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" class="">
</p>
</div>
</blockquote></div><br class=""></div></div>
_______________________________________________<br class="">GOAL mailing list<br class=""><a href="mailto:GOAL@eprints.org" class="">GOAL@eprints.org</a><br class="">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal<br class=""></div></blockquote></div><br class=""></body></html>