<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Tim Donohue</b> <span dir="ltr"><<a href="mailto:tdonohue@duraspace.org">tdonohue@duraspace.org</a>></span><br>
Date: Mon, Nov 5, 2012 at 1:18 PM<br>Subject: Re: [Dspace-general] The Importance of Repository EC- (OpenAire) and RCUK-Compliance Tags for Mandate Compliance Verification<br><br>Hi DSpace Users,<br>
<br>
I just wanted to follow up to this request to let everyone know that, as of DSpace 3.0 (coming in late November / early December), DSpace has a completely rewritten OAI-PMH interface which is now compliant with both OpenAIRE (<a href="http://www.openaire.eu/" target="_blank">http://www.openaire.eu/</a>) and DRIVER (<a href="http://www.driver-support.eu/" target="_blank">http://www.driver-support.eu/</a><u></u>).<br>
<br>
This new feature for DSpace 3.0 was provided by Lyncode (<a href="http://www.lyncode.com" target="_blank">http://www.lyncode.com</a>) and our latest DSpace Committer, João Melo.<br>
<br>
More information on this brand new OAI-PMH interface (nicknamed "OAI 2.0") can be found in the DSpace 3.0 documentation at:<br>
<br>
<a href="https://wiki.duraspace.org/display/DSDOC3x/OAI" target="_blank">https://wiki.duraspace.org/<u></u>display/DSDOC3x/OAI</a><br>
<a href="https://wiki.duraspace.org/display/DSDOC3x/OAI+2.0+Server" target="_blank">https://wiki.duraspace.org/<u></u>display/DSDOC3x/OAI+2.0+Server</a><br>
<br>
If any DSpace Users would like to try out this new, or help us test the new OAI-PMH interface in general, we are holding a second testathon this week.<br>
<br>
You can test things on our demo server: <a href="http://demo.dspace.org/" target="_blank">http://demo.dspace.org/</a><br>
OR<br>
You can download DSpace 3.0 Release Candidate #3 and install it locally to test: <a href="http://sourceforge.net/projects/dspace/files/DSpace%20Release%20Candidate/3.0-rc3/" target="_blank">http://sourceforge.net/<u></u>projects/dspace/files/DSpace%<u></u>20Release%20Candidate/3.0-rc3/</a><br>
<br>
More info on Testathon is at: <a href="https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Testathon+Page" target="_blank">https://wiki.duraspace.org/<u></u>display/DSPACE/DSpace+Release+<u></u>3.0+Testathon+Page</a><br>
<br>
Thanks!<br>
<br>
- Tim<br>
<br>
On 11/4/2012 12:32 PM, Stevan Harnad wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
/**Cross-Posted **/<br>
<br>
<br>
It is extremely important for the success of both funder and<br>
institutional OA mandates worldwide that eprints, dspace and all other<br>
repositories be made compliant with funder harvesting requirements such<br>
as those of OpenAIRE <<a href="http://www.openaire.eu" target="_blank">http://www.openaire.eu</a>> (as Eloy Rodrigues<br>
indicates in the passage appended after this message).<br>
<br>
For deposit mandates to work, they need to have /a reliable and<br>
date-stamped compliance verification mechanism/.<br>
<br>
*/Plea to repository managers and software developers //world-wide/: *<br>
<br>
This is the time to make sure that your repositories implement the<br>
requisite metadata tags for specifying the funding agency (US, EU or<br>
RCUK) as well as the article's journal acceptance date).<br>
<br>
A system must be designed for ensuring that the mandate will actually be<br>
complied with, which means that there has to be an effective, timely<br>
monitoring mechanism, with swift feedback and consequences in case of<br>
non-compliance.<br>
<br>
That means that immediate-deposit of full-text upon acceptance for<br>
publication has to be monitored continuously, based on authors' ongoing<br>
publication calendar dates not just retrospectively in 4-6-year batches.<br>
<br>
If compliance is instead left to the the latter -- long-delayed<br>
retrospective batches -- then even the talk about a "6-12-month embargo"<br>
becomes meaningless! Embargos can only be observed if publication dates<br>
are observed, and hence if deposits, whether embargoed or unembargoed,<br>
are immediate. That's how deposit-date needs to be integrated into RCUK<br>
authors' annual work-flow, including the all-important date-stamping by<br>
the official date of the journal's letter of acceptance -- not the<br>
wildly varying and incalculable date on which the journal issue actually<br>
appears -- which is in turn often far from the calendar date of<br>
publication: as much as a year or more at times.)<br>
<br>
The EC's and RCUK's mandates have to be integrated with institutional<br>
mandates so as to implement the following 8 shared conditions:<br>
<br>
(1) *immediate-deposit* (even if access to the deposit is allowed to<br>
be embargoed):<br>
(2) of the *final peer-reviewed draft*<br>
(3) on the *date of acceptance* by the journal (which is marked by a<br>
verifiable calendar date-stamp)<br>
(4) and the immediate-deposit must be directly in the *author's own<br>
institutional repository* (not institution-externally -- central<br>
repositories can harvest from IRs)<br>
(5) so that immediate-deposit can be *monitored and verified by the<br>
author's institution* (regardless of whether the mandate is from a<br>
funder or the institution)<br>
(6) as a *funding compliance condition* and/or an *institutional<br>
employment condition*<br>
(7) and institutional repository must be designated as the *sole<br>
locus of deposit * for submitting publications for institutional<br>
performance evaluation, funder conditions and national research<br>
assessment.<br>
(8) Repository deposits must be monitored so as to generate *rich<br>
and visible metrics of usage and citation* so as to verify and<br>
reward authors' deposits as well as to showcase and archive the<br>
institution's and funder's research output and impact.<br>
<br>
An instance of mututally reinforcing funder and institutional policies<br>
is the FRS-FNRS<br>
<<a href="http://openaccess.eprints.org/index.php?/archives/864-.html" target="_blank">http://openaccess.eprints.<u></u>org/index.php?/archives/864-.<u></u>html</a>> policy in<br>
Belgium.<br>
<br>
Best wishes,<br>
Stevan Harnad<br>
<br>
*On 2012-11-04, at 12:39 PM, "Eloy Rodrigues" [OpenAire] wrote:*<br>
<br>
Hi Stevan,<br>
<br>
I agree with the recommendations for compliance-verification for RCUK<br>
that I've seen in another message.<br>
<br>
Regarding OpenAIRE we tried that our infrastructure helps/cooperate<br>
(and not<br>
compete) with the network of institutional repositories. We tried to<br>
have<br>
very "low barrier" guidelines for compliance (we are now calling<br>
compatibility), basically just requiring identification of the EC<br>
project<br>
and access status (Open Access, embargoed, closed) in a "standard" way.<br>
EC funded publications will be regularly harvested from<br>
compliant/compatible<br>
repositories. So, authors from institutions with compliant repositories,<br>
just need to deposit on their repository to comply to the EC policy. And<br>
even if an author goes to the OpenAIRE portal to deposit a<br>
publication, he<br>
will be re-directed to the repository of it's own institution.<br>
<br>
But unfortunately the number of compliant repositories is still not high<br>
enough (except on some southern countries like Portugal and Spain),<br>
and is<br>
particularly low in the UK...<br>
<br>
Best,<br>
Serviços de Documentação<br>
Eloy Rodrigues<br>
Direcção<br>
Campus de Gualtar, 4710 - 057 Braga - Portugal<br>
Telefone +351 253 604 156/7/8; Fax <a href="tel:%2B351%20253%20604%20159" value="+351253604159" target="_blank">+351 253 604 159</a><br>
Campus de Azurém, 4800 058 Guimarães<br>
Telefone <a href="tel:%2B351%20253%20510%20168" value="+351253510168" target="_blank">+351 253 510 168</a>; Fax <a href="tel:%2B351%20253%20510%20117" value="+351253510117" target="_blank">+351 253 510 117</a><br>
<a href="http://www.sdum.uminho.pt" target="_blank">http://www.sdum.uminho.pt</a> | Siga-nos<br>
<br>
</blockquote>
<br>
</div><br>