Rioxx: The Research Outputs Metadata Schema


RIOXX operates in a similar space to OpenAIRE and so the RIOXX team at EDINA have been concerned to make the two metadata application profiles as mutually compatible as possible. Working closely with the OpenAIRE team, we have prepared a document which explains how to 'map' properties from RIOXX 2.0 to OpenAIRE 3.0, with some guidance also on mapping terms in some of the controlled vocabularies. This 'crosswalk' document can be found here.

The universities of Hull, Huddersfield and Lincoln, collaborating as HHuLOA, have been analysing RIOXX 2.0 in the context of implementation within their various repository systems. While Lincoln and Huddersfield have deployed ePrints, Hull has a Hydra repository. This is the first information I have seen from people intending to implement RIOXX in a Hydra system, so is very welcome! You can read a summary of their findings, or access the full report (PDF)

Following a very useful discussion with Mike Taylor (see comments on this post), I have split the validation of RIOXX records into two stages: a basic syntax check, following less strict rules and constraints than the full RCUK requirements a strict validation check against the full RCUK requirements The reason for doing this is to allow implementers to check that their software is correctly set-up. For example, if a RIOXX-enabling plugin for a repository is correctly configured, but the repository's metadata holds values for the 'version' which are not from the RCUK-approved vocabulary for versions, then records from that repository will fail the full RCUK validation test.

I am periodically surveying repositories, using a list generated by the OpenDOAR API, to see which of these are serving RIOXX 2.0 metadata records. At the time of writing, 11 repositories are declaring support for this metadata format. You can see these listed here. I think that these early adopters are all ePrints systems, using the recently developed ePrints plugin for RIOXX. For each repository, I have harvested 10 RIOXX records to examine them for compliance with the RIOXX metadata profile.

The RIOXX team is pleased to announce the release of version 2.0 of the RIOXX metadata application profile and guidelines. The following resources are now available: metadata application profile guidelines for repository managers XML Schema files and resources The team would like to acknowledge the significant support in particular of Ben Ryan (RCUK) and Ben Johnson (HEFCE) in preparing this version 2.0 release, and would also like to thank the many contributors who have offered reviews, suggestions and corrections over the last few months.

Following further public consultation and discussion with stakeholders, we have just released RIOXX 2.0 Release Candidate 2 for comment. The changes from RIOXX 2.0 Beta 1 are detailed in the release notes, but the most significant change is that we have added a recommendation to use ISNI identifiers for for organisations when named as authors, contributors or funders. We think RIOXX 2.0 is very close to being ready for its final release and are aiming for a release date of 2015-01-09.

Update: This consultation will be closed for comments at 17:00 BST on Wednesday 16th July We are pleased to release a beta version of RIOXX 2.0 for public comment. RIOXX 2.0 has been developed by EDINA and Chygrove Ltd, with significant input from RCUK. This work is endorsed by RCUK and HEFCE and has been funded and facilitated by Jisc. Background RIOXX 1 was released in April 2013 to support institutional repositories in complying with open access reporting mandates from RCUK.

I have been working with Brigitte J├Ârg of the CERIF Support Project to consider how the RIOXX application profile might be expressed in CERIF. CERIF has become the de-facto standard for data exchange between Current Research Information Systems (CRIS), particularly in Europe. In the spirit of working as openly as possible, we are sharing our thinking about this as we go. One particularly interesting aspect of this has how CERIF might handle the way in which we express cardinality constraints in the RIOXX profile (e.

The RIOXX team are pleased to announce the release of version 1.0 of the RIOXX Guidelines and Application Profile. To support the development of related software, an XML schema (XSD) has also been published Please feel free to comment on any of this work by emailing the RIOXX team at [email protected]

A minor update to the RIOXX application profile (v0.91) has been published, and a draft XSD schema intended for validation of RIOXX records has been made available. Comments on either or both are welcome. RIOXX application profile v0.91 RIOXX XSD schema These releases should be considered as 'release candidates'. Work is under way to develop plugins/patches for both ePrints and DSpace to help institutional repositories to implement the guidelines and application profile.