Balviar Notay gives us an update on the RIOXX metadata work.
With those that are concerned with complying to RCUK and HEFCE OA policies you will most likely have come across the RIOXX metadata application profile work.
The RIOXX application profile has been developed by Jisc via EDINA and Chygrove Ltd with close input from RCUK and HEFCE to meet their policy requirements.
At Open Repositories 2014 we estimated that version 2.0 of the RIOXX application profile would be released at the end of July 2014. This is now not the case as RIOXX is subsuming the outputs of the Vocabularies for Open Access (V4OA) Project which is recommending the use of NISO identifiers for open access – particularly the use of the free_to_read tag and licence_ref). NISO is still as yet to formally release their recommendations and the indication from NISO is that they plan to release the final recommendations at the end of August/early September. Whist we don’t envisage any change in the draft NISO recommendations, we don’t want to release RIOXX 2.0 until the NISO recommendations have been formally ratified.
So what does this mean for repositories and the implementation of the RIOXX application profile?
• We will start the plug-in development for ePrints and DSpace in August/September 2014 (taking into account that there might be small changes to the code in September) but we want to do the majority of the development in August.
• In October/November 2014 we want to test the plug-in with a number of early adopters. These institutions are yet to be identified and if you would like to be considered for an early adopter please reply to this blog post.
• December 2014 to April 2015 repositories to implement the RIOXX application profile and guidelines. This will support two aspects:
– This allows data to be collected with the appropriate RIOXX fields to effectively support RCUK evidence-based reviews of the effectiveness and impact of its Open Access policy. RCUK has commenced reviews for 2014 and plan to periodically review thereafter (probably in 2016 and 2018).
– This also supports institutions early planning for REF OA compliance starting 1st April 2016.
This is a tight timeline but most of the RIOXX application profile is near to complete after the public consultation and close input from RCUK and HEFCE. (Just waiting for the NISO final recommendations).We are also putting in place a layer of support for IRs through the Repository Support Project (RSP) and planning co-ordination with platform-specific support through Eprints Services, the DSpace community and Fedora.
So we plan to keep you updated and the next presentation on the RIOXX application profile will be at the repository Fringe on the 30th July 2014. http://rfringe14.blogs.edina.ac.uk/programme-2/