<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin-right:0in;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
p.msolistparagraphcxspfirst, li.msolistparagraphcxspfirst, div.msolistparagraphcxspfirst
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
p.msolistparagraphcxspmiddle, li.msolistparagraphcxspmiddle, div.msolistparagraphcxspmiddle
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
p.msolistparagraphcxsplast, li.msolistparagraphcxsplast, div.msolistparagraphcxsplast
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
p.msochpdefault, li.msochpdefault, div.msochpdefault
{margin-right:0in;
margin-left:0in;
font-size:10.0pt;
font-family:"Times New Roman","serif"}
span.emailstyle17
{font-family:"Calibri","sans-serif";
color:#1F497D}
p.Textedebulles, li.Textedebulles, div.Textedebulles
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif"}
span.TextedebullesCar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle28
{font-family:"Calibri","sans-serif";
color:#1F497D}
span.EmailStyle29
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.25in 1.0in 1.25in}
div.WordSection1
{}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Hi Marc,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Apologies for the delay in replying – I have been on the road this week.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">The introduction of tags was an idea we developed after consultation with large, mainly commercial, sharing platforms such as social collaboration networks.
For them the challenge is to handle a tsunami of user-uploaded content in an automated way. We are working to implement tagging of both final articles and manuscripts which will include information to allow platforms to automatically detect what version of
the article has been uploaded along with other key information such as the embargo end date. The availability of these metadata on full-text uploads will be particularly helpful to them.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Repositories are free to extract and use the data from the tags if they would like to do so. We will also make these metadata available for everyone to use
via our ScienceDirect API. However, not all repositories like the idea of a variety of APIs and some express the wish of a more simple method. Tagging therefore helps us to cater for differing platform needs.
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">We recognize that the development of an industry-wide API would be desirable to avoid the need for repositories to integrate with multiple APIs, and we would
support this approach.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">With kind wishes,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Alicia</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </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: +44 (0) 7823 536 826 I E:
<a href="mailto:a.wise@elsevier.com">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"; color:#1F497D"> </span></p>
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif""> goal-bounces@eprints.org [mailto:goal-bounces@eprints.org]
<b>On Behalf Of </b>Couture Marc<br>
<b>Sent:</b> Thursday, June 04, 2015 9:03 PM<br>
<b>To:</b> Global Open Access List (Successor of AmSci)<br>
<b>Subject:</b> [GOAL] Re: Update on statement against Elsevier's new "sharing" policy</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">Hi all,</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">Elsevier has a record of pretending to make its decisions (at least partly) in the interests of researchers, or research, and now repositories.</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">One example is the introduction of tagged manuscripts. I don’t really understand how it will work and what will be gained by authors or repositories if they
use these instead of the usual author-supplied manuscripts, with metadata residing in the repository itself.</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">The new policy seems to imply that either the author-provided or the Elsevier-tagged manuscripts could be self-archived, but like much of the policy, it’s far
from clear.</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">In this page (<a href="http://www.elsevier.com/connect/elsevier-updates-its-policies-perspectives-and-services-on-article-sharing">http://www.elsevier.com/connect/elsevier-updates-its-policies-perspectives-and-services-on-article-sharing</a>),
it is stated that in order to help repositories “ensure self-archived accepted manuscripts can be made available in line with publisher’s hosting & posting policies”, Elsevier will be “taking steps to tag all manuscripts from the point of acceptance with key
metadata”. And also this: “IRs will have access to the tagged manuscripts if an author self-archives.”</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">What I understand here is that these embedded metadata could be used by Elsevier to automatically, and more efficiently, monitor policy compliance (notably
embargo). Which they have certainly the right to do, by the way. The point is: do we have, or wish to work for them on this?</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">Finally, I suggest that you read the Comments section of the above-cited page, especially Ms Wise’s answers, which are - how to say it - more to the point
than what I’d been expected to find.</span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt; font-family:"Calibri","sans-serif"">Marc Couture</span></p>
</div>
<style>
<!--
-->
</style><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>
</body>
</html>