How compliant is your institution? University of Glasgow RIOXX case study - Mick Eadle, University of Glasgow

University of Glasgow RIOXX Case Study

Mick Eadie

michael.eadie@glasgow.ac.uk

How compliant is your institution?

Background

2008: Publication policy

2008: EPrints publications repository

2010: Research System Awards linked to repository

2013: Dept. for Business Innovation Skills Pump-Priming

RCUK funded Articles in Repository 2010 - 2015

0

100

200

300

400

500

600

2010 2011 2012 2013 2014 2015

RCUK Articles

Open Access

Background

How we do things…? – Centralised open access support in the Library

– Some admin support from Colleges and Schools

How to check compliance with Research Council’s UK Open Access policy?

RIOXX EPrints Plugin

• Installed Jan 2015

• Timeline (see e2eoa.org)

http://e2eoa.org

RIOXX EPrints Plugin

• How do we use?– Indicates potential gaps in compliance on data entry

RIOXX EPrints Plugin

RIOXX EPrints Plugin

RIOXX EPrints Plugin

• How do we use?– Indicates potential gaps in compliance on data entry

– Provides a packaged report / export

RIOXX EPrints Plugin

• How do we use?– Indicates potential gaps in compliance on data entry

– Provides a packaged report / export

– Some extra things we needed:

– Funder / Research Data Acknowledgement

– Financial transaction information

– Reports that map to RCUK and Charities Open Access Fund reporting template

– Shared this with the community…

http://github.org/eprintsug/OpenAccess

RIOXX EPrints Plugin

http://www.rioxx.net/implementation/#live_repositories

Compliance Considerations

• Detailed publication date not always available

• Accepted Date not clear at initial contact from author

• Licence not available at early stage

• Project funder not available at early stage

• Document not available for upload at early stage

Future Plans

• DatesDatesDates

• New REF Plugin (hefce_oa) – how does this integrate with RCUK tool?

• Improved reports for College compliance (incl. visuals)

• Work with EPrints community avoid duplication