RIOXX: What is it? Why create it? What does it mean for Dspace users?

RIOXX: What is it? Why create it? What does it mean for Dspace users?

RIOXX 2 Overview What is RIOXX? UK and EC OA policies The roles of repositories How RIOXX developed in the UK And is still developing? Key information needed for RIOXX How it can be collected DSpace adoption roadmap Questions / discussion?

RIOXX 3 RIOXX»Metadata application profile»implementation guidance for repositories»technical support for uptake www.rioxx.net

RIOXX 4 UK and EC policies Policy Journal articles / published conference papers Monographs RCUK ( 2.3bn p.a.) Wellcome Trust ( 700m p.a.) REF (1.6bn p.a.) EC Horizon 2020 ( 67bn over six years) Immediate Gold OA, under CC-BY, APC paid, or Embargoed Green OA Immediate Gold OA, under CC-BY, APC paid, or Embargoed Green OA Deposit at acceptance Discoverable by publication OA within ~RCUK embargo limits Deposit by publication Immediate Gold OA, APC paid, or Embargoed Green OA No requirement, but encouragement and active consideration Immediate Gold OA, under CC-BY- NC/D, BPC paid, or Embargoed Green OA No requirement this time, but active consideration for future No requirement this time, but encouragement Funding for FP7

RIOXX 5 The roles of repositories Policy Roles of repositories RCUK ( 2.3bn p.a.) Wellcome Trust ( 700m p.a.) REF (1.6bn p.a.) EC Horizon 2020 ( 67bn over six years) Manage and share Green OA material Capture management information to support compliance reporting Improve discovery of OA material No significant role for institutional repositories Europe PubMedCentral central facility EPMC passes material to institutional repositories via Publications Router Hold deposited items, release OA after embargo Record and expose metadata to improve discovery Capture management information to support compliance reporting Hold deposited items, release OA after embargo Record and expose metadata to improve discovery - OpenAIRE Capture management information to support compliance reporting

RIOXX 6 How RIOXX developed in the UK A long and winding path 2013 2014 2015 RIOXX1.5 V4OA RIOXX2.0 Need for more consistent vocabularies for key OA fields NISO OA metadata group -> LicenceRef and Free-to-read RCUK policy and some information about audit and reporting requirements REF policy, but little information about audit and reporting EC OpenAIRE guidelines; pressure for UK to comply -> Close working with RCUK and REF staff, and OpenAIRE More detail on RCUK and REF requirements Jisc now a member of OpenAIRE: compliance via RIOXX/CORE-OpenAIRE mapping International groups looking at alignment COAR Still evolving. CASRAI

RIOXX 7 Key information needed for RIOXX /1 Field Status Control Source ali:free_to_read Optional Defn: NISO Date: ISO8601 ali:license_ref Mandatory Defn: NISO http URI Start date: ISO8601 Repository manager / publisher CrossRef? But URIs for all rights reserved / embargoed Elsevier policy dc:identifier Mandatory http URI for file Repository software (note separate RIOXX records for each copy) dc:publisher Recommend ed Recommend control list dc:source (Mandatory) Recommend ISSN/iSBN Eg Sherpa/RoMEO Eg Sherpa/RoMEO http://rioxx.net/guidelines/rioxx_metadata_guidelines_v_3.0.pdf

RIOXX 8 Key information needed for RIOXX /2 Field Status Control Source dcterms:dateaccepte d Mandatory Date: ISO8601 Publishers? rioxxterms:author Mandatory ID attribute ORCID / ISNI recommended rioxxterms:project Mandatory ID (ISNI or FundRef DOI) or name ORCID (note UK take-up) ISNI, FundRef Via institutional systems rioxxterms:type Mandatory List of terms given Repository workflow rioxxterms:version Mandatory List of terms given, adapted from NISO JAV recommendations rioxxterms: version_of_record Recomme nded http URI (http version of DOI where available) Repository workflow CrossRef http://rioxx.net/guidelines/rioxx_metadata_guidelines_v_3.0.pdf

RIOXX 9 Publishers can help But it is the responsibility of the author / university Send manuscript to all authors and their institutions on acceptance Work with emerging Jisc services Fully exploit technical standards and services Be clear about permissions So that they can be deposited into repositories for the REF So that universities and publishers can save time and effort in managing many-to-many relationships So university systems can pull in the information they need So authors and institutions know whether / how they can comply with OA policies»see Jisc website for more details http://scholarlycommunications.jiscinvolve.org/

RIOXX 10 DSpace adoption roadmap RIOXX2.0 released DSpace add-on for v5.0 (with back port compatibility to 3.x / 4.x). Technical support for repository managers REF support plug-in, capturing additional information needed CASRAI OA reporting working group COAR, CASRAI, OpenAIRE, La Referencia join-up controlled vocabularies.. Jan 2015 Beta testing June 2015. Final release? Some in place now. More to come Currently being scoped July 2015???

Contact Neil Jacobs Head of Scholarly Communications Support neil.jacobs@jisc.ac.uk www.jisc.ac.uk Except where otherwise noted, this work is licensed under CC-BY-NC-ND