{"id":1616,"date":"2014-07-30T12:44:03","date_gmt":"2014-07-30T11:44:03","guid":{"rendered":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/?p=1616"},"modified":"2014-08-07T09:09:13","modified_gmt":"2014-08-07T08:09:13","slug":"rioxx-v2-0","status":"publish","type":"post","link":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/2014\/07\/rioxx-v2-0\/","title":{"rendered":"RIOXX v2.0"},"content":{"rendered":"<p>Original concerns for <a href=\"http:\/\/rioxx.net\/\">RIOXX<\/a>:<\/p>\n<ul>\n<li>Primary:\n<ul>\n<li>How to represent the funder<\/li>\n<li>How to represent the project\/grant<\/li>\n<\/ul>\n<\/li>\n<li>Secondary:\n<ul>\n<li>How to represent the persistent identifier of the item described<\/li>\n<li>Provisions of identifiers pointing to related data sets<\/li>\n<li>How to represent the terms of use for an item<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Original principles:<\/p>\n<ul>\n<li>Purpose driven &#8211; Focussed on satisfying RCUK reporting requirements<\/li>\n<li>Simple (re-use DC, not CERIF)<\/li>\n<li>Generic in scope (don&#8217;t tie down to specific types o output)<\/li>\n<li>Interoperable &#8211; specifically with OpenAIRE<\/li>\n<li>Developed openly &#8211; public consultation<\/li>\n<\/ul>\n<p>Has anything changed with <a href=\"http:\/\/rioxx.net\/v2-0-beta-1\/\">RIOXX 2 (mid-2014)<\/a>?<\/p>\n<ul>\n<li>Still purpose driven, but no encompassing HEFCE requirements as well<\/li>\n<li>Slightly more sophisticated \/ complex but still quite simple<\/li>\n<li>No longer &#8216;generic&#8217; &#8211; explicit focus on publications<\/li>\n<li>No longer seen as a temporary measure &#8211; positioned to support REF2020<\/li>\n<li>Interoperability still key &#8211; and currently working on an OpenAIRE crosswalk<\/li>\n<\/ul>\n<p>Other changes:<\/p>\n<ul>\n<li>Implementing recommendations from the V4OA process\n<ul>\n<li>controlled vocabs for rioxxterms:version, rioxxterms:apc<\/li>\n<li><a href=\"http:\/\/www.niso.org\/workrooms\/oami\/\">Use of NISO&#8217;s Open Access Metadata and Indicators<\/a> (licence_ref)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Current status:<\/p>\n<ul>\n<li>version 2.0 beta was released for public consultation in June 2014<\/li>\n<li>version 2.0 RC 1 has been compiled<\/li>\n<li>accompanying guidelines are being written<\/li>\n<li>XSD schema beeen developed<\/li>\n<li>expect full release in late August\/early September<\/li>\n<\/ul>\n<p>Some specific elements:<\/p>\n<ul>\n<li>dc:identifier\n<ul>\n<li>identifies the open access item being described by the RIOXX metadata record, regardless of where it is<\/li>\n<li>recommended to identify the resource itself, not a splash page<\/li>\n<li>dc:identifier MUST be an HTTP URI<\/li>\n<\/ul>\n<\/li>\n<li>dc:relation and rioxxterms:version_of_record\n<ul>\n<li>rioxxterms:version_of_record is an HTTP URI which is a persistent identifier for the published version of a resource<\/li>\n<li>will often be the HTTP URI form of a DOI<\/li>\n<\/ul>\n<\/li>\n<li>dc:relation\n<ul>\n<li>option property pointing to other material (e.g. dataset)<\/li>\n<\/ul>\n<\/li>\n<li>dcterms:dateAccepted\n<ul>\n<li>MUST be provided<\/li>\n<li>more precise than other dated events (&#8216;published&#8217; date very grey area)<\/li>\n<\/ul>\n<\/li>\n<li>rioxxterms:author &amp; rioxxterms:contributor\n<ul>\n<li>MUST be HTTP URIs &#8211; ORCID strongly recommended<\/li>\n<li>one rioxxterms:author per author<\/li>\n<li>rioxxterms:contributor is for parties that are not authors but credited with some contribution to publication<\/li>\n<\/ul>\n<\/li>\n<li>rioxxterms:project\n<ul>\n<li>joins funder and projected in one, slightly more complex, proerty<\/li>\n<li>The use of funder IDs (DOIs in their HTTP URI form) from <a href=\"http:\/\/www.crossref.org\/fundref\/\">FundRef<\/a> is recommended, but other ID schemes can be used and name can be used<\/li>\n<\/ul>\n<\/li>\n<li>license_ref\n<ul>\n<li>adopted from <a href=\"http:\/\/www.niso.org\/workrooms\/oami\/\">NISO&#8217;s Open Access Metadata and Indicators<\/a><\/li>\n<li>takes an HTTP URI and a start date<\/li>\n<li>URI should identify a license\n<ul>\n<li>there is work under way to create a &#8216;white list&#8217; of acceptable licenses<\/li>\n<\/ul>\n<\/li>\n<li>embargoes can be expressed by using the &#8216;start date&#8217; to show the date on which the license takes effect<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Funding of development of RIOXX as application profile now at an end, but funding for further developments (e.g. s\/w development for repositories etc.)<\/p>\n<p>RIOXX is endorsed by both RCUK and HEFCE<\/p>\n<p>Q: What about implementing RIOXX in CRIS systems?<\/p>\n<p>A: Some work on mapping between CERIF and RIOXX, although not ongoing work. Technical description available for any one to implement.<\/p>\n<p>A (Balviar): In terms of developing plugins for commercial products &#8211; not talked to commercial suppliers yet, but planning to look at what can be developed and conversations now starting.<\/p>\n<p>A (James): Already got RIOXX terms in Pure feed at Edinburgh<\/p>\n<p>Q: Can you clarify &#8216;first name author&#8217; vs &#8216;corresponding author&#8217; &#8211; do you intend the first named author to be the corresponding author?<\/p>\n<p>A: Understand that the &#8216;common case&#8217; is that the first name author is the corresponding author [at this point lots of disagreement from the floor on this point].<\/p>\n<p>&#8216;first name author&#8217; seen as synonym for &#8216;lead author&#8217;<\/p>\n<p>Q: Why is vocabulary for (?) not in line with REF vocabulary<\/p>\n<p>A: HEFCE accepts wider range of outputs that &#8216;publications&#8217;, but RIOXX specifically focusses on publications \u00a0&#8211; where most OA issues lie<\/p>\n<p>Q: &#8216;Date accepted&#8217; what about historic publications? Won&#8217;t have date of acceptance<\/p>\n<p>A: RIOXX not designed for retrospective publication &#8211; going forward only. Not a general purpose bibliographic record<\/p>\n<p>Comment from Peter Burnhill: RIOXX is not a cataloguing schema &#8211; it is a set of labels<\/p>\n<p>Paul W emphasises &#8211; RIOXX is not a &#8216;record&#8217; format &#8211; the systems outputting RIOXX will have much richer metadata already. There is no point in &#8216;subverting&#8217; RIOXX for historical purposes &#8211; this isn&#8217;t its intended purpose.<\/p>\n<p>Q: Can an author have multiple IDs in RIOXX<\/p>\n<p>A: Not at the moment. Mapping between IDs for authors is a different problem space, not one that RIOXX tries to address<\/p>\n<p>Comment from RCUK: Biggest problem is monitoring compliance with our policies &#8211; which RIOXX will help with a lot<\/p>\n<p>Comments from floor: starting to see institutions issues ORCIDs for their researchers &#8211; could see multiple ORCIDs from a single person. Similarly with DOIs &#8211; upload a publishers PDF to Figshare you get a new DOI<\/p>\n<p>Q: If you are producing RIOXX what about OpenAIRE<\/p>\n<p>A:\u00a0There is nothing in RIOXX that would stop it being OpenAIRE compliant &#8211; so RIOXX records can be transformed into OpenAIRE records (but no vice versa)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Original concerns for RIOXX: Primary: How to represent the funder How to represent the project\/grant Secondary: How to represent the persistent identifier of the item described Provisions of identifiers pointing to related data sets How to represent the terms of use for an item Original principles: Purpose driven &#8211; Focussed on satisfying RCUK reporting requirements [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[98],"class_list":["post-1616","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-rfringe14"],"_links":{"self":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1616","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/comments?post=1616"}],"version-history":[{"count":5,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1616\/revisions"}],"predecessor-version":[{"id":1649,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/posts\/1616\/revisions\/1649"}],"wp:attachment":[{"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/media?parent=1616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/categories?post=1616"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.meanboyfriend.com\/overdue_ideas\/wp-json\/wp\/v2\/tags?post=1616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}