| Popis: |
This contribution considers recent updates to Rioxx, the Research Outputs Metadata Schema [1]. Originally an OAI-PMH metadata application profile for open repositories in the UK, Rioxx version 2.0 has been broadly supported by institutional repositories in the UK since 2016 and has also enabled a level of OpenAIRE participation from institutions for whom compliance was always problematic [2]. More recently Rioxx has entered candidate release status for version 3.0 in which a more holistic and less UK centric approach to the schema has been adopted. This approach has sought to continue the schema’s previously evidenced harvesting and aggregation benefits [3] while also improving the capture of graph relations to other scholarly entities. Rioxx 3.0 introduces superior modelling of associative relationships between scholarly entities, harnesses greater use of persistent identifiers (PIDs), and reuses semantics from schema.org [4] while retaining OAI-PMH as the principal data harvesting mechanism. The schema delivers a useful contribution to burgeoning open scholarly graphs since it can better model relational associations between scholarly entities, enabling research organizations to capture these relations at deposit source and contribute them to the graph via aggregation services, such as CORE [5,6]. Such data once aggregated, and merged with existing PID data, has the potential to greatly enrich the formal PID graph but also enhance user discovery of related research entities, most notably research publications, datasets, software, projects, and grants. Explicit encoding of resource deposit and exposure dates further presents opportunities for better tracking open access growth and monitoring the evolution of this growth at scale. This contribution will explore examples of features from the Rioxx candidate release, exploring the significance of the changes between version 2.0 and 3.0, and demonstrating some of its relational potential with respect to the scholarly graph. We will also consider the deployment of schema.org vocabularies as a useful, semantically interoperable mechanism for better communicating output type semantics. Future developments, such as the creation of a new Rioxx validator within the CORE repository dashboard, will be briefly summarized. |
