<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
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
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></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 all,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I suspect compliance enforcement isn’t such an issue for NIH because so many publishers deposit on behalf of their authors. It’s one of the ways publishers have constructively engaged with the NIH on implementation of its open access policy. Elsevier has deposited manuscripts into PMC on behalf of authors since 2005, for example.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>With kind wishes,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Alicia<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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>Michael Eisen<br><b>Sent:</b> 25 April 2012 15:49<br><b>To:</b> Global Open Access List (Successor of AmSci)<br><b>Subject:</b> [GOAL] Re: OA and NIH public access compliance and enforcement?<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'>The NIH enforces the policy by requiring a PMC ID on every paper submitted with grant progress reports and renewals. It's actually fairly effective. <o:p></o:p></p><div><p class=MsoNormal>On Mon, Apr 23, 2012 at 8:02 PM, Stevan Harnad <<a href="mailto:harnad@ecs.soton.ac.uk" target="_blank">harnad@ecs.soton.ac.uk</a>> wrote:<o:p></o:p></p><p class=MsoNormal>Hard to imagine how fundee compliance with NIH OA policy can be<br>effectively enforced while:<br><br>(1) Deposit can be done by either the fundee or the publisher<br>(who is not bound by the grant's conditions)<br><br>(2) Deposit must by directly in PubMed Central instead<br>of the fundee's institutional repository (where the institution<br>can monitor publication output and ensure compliance)<br><br>Unlike the institution (which monitors its researchers'<br>publication output and productivity) the funder is unaware<br>of what and where papers are published, especially after<br>peer review is done and the researcher is funded. (Final<br>Reports come far too late.)<br><br>Hence the natural enforcer for funder policy is of course the<br>fundee's institution, which already casts an eager eagle eye<br>on all phases of the all-important research application and<br>funding process (because of a shared institutional interest<br>in getting research funding).<br><br>The publisher, in contrast, has every interest in deterring or<br>delaying OA as much as possible.<br><br>The researcher, meanwhile, is busy writing grant applications<br>and conducting research, if funded. Publish-or-perish ensures<br>that researchers publish, but only institutions and institutional<br>mandates can ensure that the publications are made OA<br>(especially if institutional repository deposit is designated<br>as the sole mechanism for submitting research for annual<br>institutional performance review).<br><br>See <a href="http://bit.ly/institutionalOA" target="_blank">http://bit.ly/institutionalOA</a><br><br>Stevan Harnad<br><br>On 2012-04-23, at 8:03 PM, LIBLICENSE wrote:<br><br>> From: "Hansen, Dave" <<a href="mailto:drhansen@email.unc.edu">drhansen@email.unc.edu</a>><br>> Date: Mon, 23 Apr 2012 21:28:06 +0000<br>><br>> Does anyone on this list have an idea of how the NIH enforces its<br>> public access policy? I recently had a conversation with someone who<br>> has viewed several NIH non-compliance letters. She expressed some<br>> consternation that, while letters sometimes go out about<br>> non-compliance, there is no real force behind them and nothing that<br>> effectively compels compliance. I couldn’t find any more info from the<br>> NIH itself.<br>><br>> Does anyone have any idea how prevalent non-compliance is and how<br>> frequently NIH takes actions to enforce the policy, and for those<br>> library lawyers that I know lurk around on this list, who (if anyone)<br>> would be able to contest non-enforcement by the NIH?*<br>><br>> *I’m not trying to pick a fight. I’d just like to know who has the<br>> right to do such a thing.<br>><br>> -----<br>><br>> David R. Hansen<br>> Digital Library Fellow<br>> Samuelson Law, Technology & Public Policy Clinic<br>> UC Berkeley School of Law<br>> <a href="mailto:dhansen@law.berkeley.edu">dhansen@law.berkeley.edu</a><br>> <a href="tel:%28510%29%20643-8138">(510) 643-8138</a><br><br><br>_______________________________________________<br>GOAL mailing list<br><a href="mailto:GOAL@eprints.org">GOAL@eprints.org</a><br><a href="http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal" target="_blank">http://mailman.ecs.soton.ac.uk/mailman/listinfo/goal</a><o:p></o:p></p></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <br>Michael Eisen, Ph.D.<br>Investigator, Howard Hughes Medical Institute<br>Associate Professor, Department of Molecular and Cell Biology<br>University of California, Berkeley<o:p></o:p></p></div></div></body></html>
<pre>Elsevier Limited. Registered Office: The Boulevard, Langford Lane, Kidlington, Oxford, OX5 1GB, United Kingdom, Registration No. 1982084 (England and Wales).