<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:m="http://schemas.microsoft.com/office/2004/12/omml" 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 14 (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:0cm;
        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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";
        mso-fareast-language:EN-AU;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";
        mso-fareast-language:EN-US;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>The Australian situation is interspersed – nothing to do with REF and HEFCE, but our equivalent research evaluation process. I provide this for comparison. <o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>Arthur Sale<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>University of Tasmania, Australia<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Repositories discussion list [<a href="mailto:JISC-REPOSITORIES@JISCMAIL.AC.UK">mailto:JISC-REPOSITORIES@JISCMAIL.AC.UK</a>] <b>On Behalf Of </b>Stevan Harnad<br><b>Sent:</b> Saturday, 16 March 2013 1:15 PM<br><b>To:</b> <a href="mailto:JISC-REPOSITORIES@JISCMAIL.AC.UK">JISC-REPOSITORIES@JISCMAIL.AC.UK</a><br><b>Subject:</b> Re: Harnad Comments on Proposed HEFCE/REF Green Open Access Mandate<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><p class=MsoNormal>On Fri, Mar 15, 2013 at 11:56 AM, Graham Triggs <<a href="mailto:grahamtriggs@gmail.com" target="_blank">grahamtriggs@gmail.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal>On 14 March 2013 22:14, 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><span style='color:#222222'>Why is it an absurd requirement to deposit immediately in the author's IR, regardless of whether the </span><o:p></o:p></p><p class=MsoNormal>journal is subscription or OA and of whether the deposit is embargoed or immediate OA?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>That simple, natural, uniform local deposit procedure is precisely what makes it easy for an institution <o:p></o:p></p><p class=MsoNormal>to monitor compliance. <o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] But of course it is totally irrelevant. Compliance has no link with deposit in the case of already OA articles, and indeed is not even easy to determine. Any senior manager (I was one) would want much better compliance certification than a deposit! Some IRs have so low visibility on the Internet as to be below the radar. I don’t want to publicise them, because they are incompetent.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>imho, there are some significant unanswered questions regarding the HEFCE/REF proposals, which ultimately boil down to a couple of points. The main one actually being covered by what you've said above.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sure, an institution can monitor compliance. In fact, as they run the repository, they are the only ones that can effectively monitor compliance. So how exactly are the requirements going to be audited and enforced?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>There is no requirement to make the metadata public. There is no requirement to have the metadata harvested (whether public or not). There isn't even a requirement to have a "request a copy" feature (without which, the usefulness of immediate deposit is rather lost).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>And nor can there be in any useful time period for the first post-2014 REF. These things will take time to build and/or implement. So there isn't any effective way to audit that deposits were made, much beyond actually being fully open access when the embargo ends at best, and possibly even only at the time of the return at worst.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I think you are mistaken -- and that you are vastly under-estimating the reach of this simple REF/HEFCE policy:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(1) It is <i>institutions</i> that have always shown intense eagerness and initiative in ensuring that their researchers comply with all RAE and REF conditions. <o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] Australian institutions have shown zero eagerness, but respond to compulsion. Otherwise they would not get grants. Strong incentive. Low initiative.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal>(2) The proposed REF mandate makes it very explicit that <i>REF submissions are ineligible if they are not deposited immediately upon publication</i>. (No waiting till near the end of the 6-year REF cycle to deposit.)<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] Australian universities have sent annual publication data to the Australian Government for well over 20 years. Not full-texts sure, but the reporting cycle is entrenched in HERDC. Compulsory.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(3) Compliance is based on two objective, verifiable data-points: publication date and IR deposit date.<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] No comment. A REF issue. Not relevant to Australia. In our case, publication in a freely chosen OA outlet = OA. An IR deposit date is not needed and indeed completely irrelevant. I have pointed out that IR deposit is equivalent to “double work” in such cases.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(4) Institutions, in monitoring and ensuring compliance will simply require -- at least annually -- a list of articles published, together with publication date and deposit date.<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] As I said we’ve done this for 20+ years, without the deposit. The returns are provided to Canberra each March or thereabouts.<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(5) If the publication date and the deposit date are not the same, the article is ineligible for REF.<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] An arcane REF rubric. Clumsy and simplistic, like smoke from the Sistine Chapel. An author publishing in an OA journal (if ignored) might be able to sue REF/HEFCE as their article was OA immediately on publication, or otherwise if they deposited before publication or a day or two after. The author could even be temporarily on the other side of the world, and living in a different day! (It happens to me every day as I am currently 11h ahead of GMT.)<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(6) With deposit, the metadata are immediately accessible web wide (though the full-text might be embargoed for the allowable interval).<o:p></o:p></p><p class=MsoNormal><span style='font-family:"Calibri","sans-serif";color:red'>[Arthur] Even without deposit, this could be true. Though I concede, unlikely to be actioned very often. However I routinely put drafts on OA even before publication, updating them later.</span><span style='font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>