Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Implementing RIOXX


Published on

Presentation on RIOXX to the Scottish Digital Library Consortium

Published in: Education
  • Be the first to comment

  • Be the first to like this

Implementing RIOXX

  1. 1. Paul Walk Head of Technology Strategy and Planning, EDINA @paulwalk Implementing RIOXX
  2. 2. …let us know a bit more about RIOXX so that we can discuss how it might be applied in the context of DSpace repositories.
  3. 3. contents • the need for RIOXX • RIOXX in detail (some specifics) • support for RIOXX implementation (in DSpace)
  4. 4. the need for RIOXX
  5. 5. why build RIOXX? • new policies from RCUK and HEFCE mandate that any journal article funded by research grants be made publicly accessible in a repository • these policies require that universities make metadata about such papers easily discoverable • the available metadata formats were inadequate • OAI-DC was not rich enough • OpenAIRE was better but demanded project IDs be encoded in particular syntax not compatible with project IDs from UK Research Councils • OpenAIRE syntax • info:eu-repo/grantAgreement/Funder/FundingProgram/ProjectID/ [Jurisdiction]/[ProjectName]/[ProjectAcronym] • RCUK syntax: • OpaqueProjectID/version
  6. 6. particular concerns • how to represent the funder • how to represent the project/grant • implementing recommendations from the V4OA process: • controlled vocabularies for rioxxterms:version, rioxxterms:apc • use of NISO’s Open Access Metadata and Indicators (license_ref and free_to_read) • how to represent the persistent identifier of the item described • provisions of identifier(s) pointing to related dataset(s) • how to represent the rights of use of the item described
  7. 7. principles • purpose driven • designed to meet a singe, focussed use-case • solve one problem well, avoid ‘feature creep’ • focussed on implementation • has to be relatively easy to implement • ‘shallow’ structure • the simplest thing that can possibly work • open development • public consultation • tested openly • rapid development • short iterations
  8. 8. RIOXX in detail (some specifics)
  9. 9. • an application profile using properties from 4 namespaces: • 11 properties from Dublin Core (dc and dcterms) • 2 properties from NISO Open Access Metadata and Indicators • 8 from a new namespace - ‘rioxxterms’ • constraints imposed through several controlled vocabularies • it has one purpose: to provide a mechanism to help institutional repositories in the UK comply with the RCUK policy on open access. • it is not designed to provide general interoperability!! • born at UKOLN, developed by EDINA and Chygrove Ltd., supported by Research Councils UK (RCUK) & Higher Education Funding Councils of England (HEFCE) and funded (initially) by Jisc • Version 2.0 released in January 2015
  10. 10. components of RIOXX • a metadata ‘application profile’ • technical documentation • an XSD schema to facilitate metadata validation • mapping to OpenAIRE 3 • a set of guidelines for systems implementation (with a focus on institutional repositories) • implementation monitoring and testing framework • a supporting website ( • (+ independent development of software plugins etc. to support RIOXX implementation)
  11. 11. some specific properties • dc:identifier • dc:relation & rioxxterms:version_of_record • dcterms:dateAccepted • rioxxterms:author & rioxxterms:contributor • rioxxterms:project • license_ref
  12. 12. dc:identifier • identifies the open access item being described by the RIOXX metadata record. • regardless of where it is located • recommended to identify the resource itself, not a ‘splash page’ • this will not always be possible or desirable • whatever it identifies, it MUST be an HTTP URI • Example: <dc:identifier> </dc:identifier>
  13. 13. dc:relation & rioxxterms:version_of_record • rioxxterms:version_of_record • an HTTP URI which is a persistent identifier for the published version of the resource • will often (normally?) be a DOI • dc:relation • optional property containing an HTTP URI identifying related resources (e.g. research data sets, software source code etc.)
  14. 14. dcterms:dateAccepted • this MUST be provided • is more precise than other possible dated events - such as ‘published’
  15. 15. rioxxterms:author & rioxxterms:contributor • both of these accept an optional ‘ID’ attribute • this MUST be an HTTP URI • use of ORCID is strongly recommended • all authors should be represented as individual rioxxterms:author properties • the ‘first named author’ can be indicated with another optional attribute called, er…, ‘first-named-author’ • rioxxterms:contributor is for other parties that are not authors but are credited with contributing in some way to the publication • Example: <rioxxterms:author id=" 0000-0002-1395-3092"> Lawson, Gerald </rioxxterms:author>
  16. 16. rioxxterms:project • this expresses funder and project_id in one, slightly more complex, property • the use of global IDs, e.g. International Standard Name Identifier (ISNI) for funding organisations is recommended • Example: <rioxxterms:project funder_name="Engineering and Physical Sciences Research Council" funder_id="" > EP/K023195/1 </rioxxterms:project>
  17. 17. license_ref • adopted from NISO’s Open Access Metadata and Indicators • takes an HTTP URI and a start date • the URI should identify a license • there is work under way to create a ‘white list’ of acceptable licenses • embargoes can be expressed this way, with a license identified to ‘take effect’ at some (possibly) future date • Example: <ali:license_ref start_date=“2015-02-17”> </ali:license_ref>
  18. 18. support for RIOXX implementation (in DSpace)
  19. 19. supporting website:
  20. 20. DSpace patch • developed by @mire • specified and funded by Jisc • • no online supporting information (as far as I can tell) but an email address to contact for info
  21. 21. open, community support • engagement from software suppliers • community feedback • good practice starting to be identified and discussed here
  22. 22. continuous testing
  23. 23. continuous testing - reporting
  24. 24. variable compliance • ePrints exposes records as ‘RIOXX’ when they are not even valid at a basic level • the DSpace patch from @mire will, allegedly, not do this. • “In the DSpace patch, items are only visible in the RIOXX OAI-PMH endpoint when they provide the mandatory fields. More details: •”
  25. 25. OpenAIRE Mapping
  26. 26. 39 repositories 4 aggregation systems …in less than one year!
  27. 27. Paul Walk Head of Technology Strategy and Planning, EDINA @paulwalk thanks for listening! the RIOXX metadata application profile is maintained & supported by EDINA: