Capturing and Reporting Open Access Metadata in Hydra/Fedora

One of the deliverables of the End to End Open Access project is ‘Capturing and Reporting Open Access Metadata in Hydra Fedora’, which Lancaster University have been working on over the past couple of months. We are no longer working on incorporating Open Access metadata in Hydra, primarily because this is the focus of the HHuLOA project and there is no point in replicating the same effort. Instead, we will demonstrate the same for Fedora (specifically for Fedora 4), providing a more open way of incorporating Open Access metadata directly in Fedora. This will provide guidance to institutions who want to deploy Fedora as a publications repository to be compliant with Open Access requirements.

One of the key requirements for any repository to be Open Access compliant, at the minimum, is supporting RIOXX. RIOXX is still quite new to many institutions and also to vendors of repositories and CRIS systems (e.g. Pure from Elsevier at this time does not support full RIOXX compliance). At the same time, many institutions are also conflicted with the complicated setup of a Fedora repository and the perceived complications of customising Fedora to incorporate Open Access compliance. The work, undertaken at Lancaster, is to show that it is technically possible to incorporate RIOXX compliance in Fedora, especially as Fedora stands Out of the Box (OOTB). This is to ensure that customers who are experimenting with Fedora can straight away understand how to add custom metadata fields and use these fields to further report on OA compliance.

A full case study will be delivered on this in the upcoming months. We will be concentrating on the Journal Article type, picking up some real examples from Lancaster University publications repository and show casing how RIOXX application profile can be implemented for these journal articles. For details, please stay tuned.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.