Crosswalk from RIOXX 2.0 to OpenAIRE 3.0

This crosswalk has been developed by the RIOXX team at EDINA in close collaboration with technical personnel at OpenAIRE. We would like to thank, in particular, Jochen Schirrwagen and Paolo Manghi for their assistance with this.

For guidance on the exact representation of properties within the OpenAIRE 3.0 metadata profile, please consult the documentation OpenAIRE Guidelines: For Literature Repositories

The terms MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL used in the table below should be interpreted as described in RFC 2119.

RIOXXOpenAIREImplementation
ali:free_to_read
Zero or one
dc:rights
One or more
This MUST be included, if available. 
ali:license_ref
One or more
dc:rights
One or more
This MUST be included, if available. 
dc:coverage
Zero or one
dc:coverage
Zero or more
This SHOULD be included, if available. 
dc:description
Zero or more
dc:description
zero or more
This MUST be included, if available. 
dc:format
Zero or more
dc:format
Zero or more
This SHOULD be included, if available. If provided in the RIOXX record, values will be in the form of MIME types
dc:identifier
Exactly one
dc:identifier
One or more
This MUST be included. This value will be in the form of an HTTP URI
dc:language
One or more
dc:language
Zero or more
This MUST be included. Values will be in the format specified by ISO 639–3
dc:publisher
Zero or more
dc:publisher
Zero or more
This MUST be included, if available. 
dc:relation
Zero or more
dc:relation
Zero or more
This SHOULD be included, if available. If provided in the RIOXX record, values will be in the form of HTTP URIs
dc:source
Zero or one
dc:source
Zero or more
This SHOULD be included, if available. If provided in the RIOXX record, the values will normally be in the form of an ISBN13 number (although this is not guaranteed)
dc:subject
Zero or more
dc:subject
Zero or more
This MUST be included, if available. 
dc:title
Exactly one
dc:title
One or more
This MUST be included. 
dcterms:dateAccepted
Exactly one
dc:date
One or more
This MUST be included. The RIOXX property (in ISO8601 ‘YYYY-MM-DD’ format) MUST be translated into the appropriate OpenAIRE URI (info:eu-repo/semantics/dateAccepted/YYYY-MM-DD).

Example: RIOXX property:

  <dcterms:dateAccepted>
    2015-03-16
  </dcterms:dateAccepted>

becomes OpenAIRE property:

  <dc:date>
    info:eu-repo/semantics/dateAccepted/2015-03-16
  </dc:date>
rioxxterms:apc
Zero or one

This MUST NOT be included. There is no mapping from RIOXX to OpenAIRE for this property, so it MUST be ignored
rioxxterms:author
One or more
dc:creator
One or more
This MUST be included. Where the RIOXX property has the optional ID attribute included, this must be appended to the text content of the OpenAIRE property, parenthesised with square brackets.

Example: RIOXX property:

  <rioxxterms:author id="http://orcid.org/0000-0002-1395-3092">
    Lawson, Gerald
  </rioxxterms:author>

becomes OpenAIRE property:

  <dc:creator>
    Lawson, Gerald [http://orcid.org/0000-0002-1395-3092]
  </dc:creator>
rioxxterms:contributor
Zero or more
dc:contributor
Zero or more
This SHOULD be included, if available. Where the RIOXX property has the optional ID attribute included, this must be appended to the text content of the OpenAIRE property, parenthesised with square brackets.

Example: RIOXX property:

  <rioxxterms:contributor id="http://isni.org/isni/0000000419367988">
    University of Edinburgh
  </rioxxterms:contributor>

becomes OpenAIRE property:

  <dc:contributor>
    University of Edinburgh [http://isni.org/isni/0000000419367988]
  </dc:contributor>
rioxxterms:project
One or one
dc:relation
Zero or more
This MUST be included. The RIOXX property includes the ‘project ID’ as provided by the funder. Funding information available and supported by OpenAIRE can be found at http://api.openaire.eu/. Where the funder is the European Commision, the mapping will be carried out as indicated in the following example:

RIOXX property:

<rioxxterms:project
  funder_name="European Commission"
  funder_id="http://isni.org/isni/000000012162673X"
>
  info:eu-repo/grantAgreement/EC/FP7/244909/EU/Making Capabilities Work/WorkAble
</rioxxterms:project>

becomes OpenAIRE property:

<dc:relation>
  info:eu-repo/grantAgreement/EC/FP7/244909/EU/Making Capabilities Work/WorkAble
</dc:relation>
rioxxterms:publication_date
Zero or one
dc:date
One or more
This MUST be included, if available and in a compatible format. If the RIOXX property is provided in ISO8601 ‘YYYY-MM-DD’ format then MUST be simply mapped into the OpenAIRE dc:date property

Example: RIOXX property:

  <rioxxterms:publication_date>
    2015-03-16
  </rioxxterms:publication_date>

becomes OpenAIRE property:

  <dc:date>
    2015-03-16
  </dc:date>

or, RIOXX property:

  <rioxxterms:publication_date>
    2015
  </rioxxterms:publication_date>

becomes OpenAIRE property:

  <dc:date>
    2015
  </dc:date>

However, rioxxterms:publication_date does not constrain the format of its values so entries such as ‘Spring, 2015’, while not permissible in OpenAIRE, are perfectly possible in RIOXX. In such cases, the mapping process may choose to parse the permissible value from the RIOXX property to use in the OpenAIRE property - so:

RIOXX property:

  <rioxxterms:publication_date>
    Spring, 2015
  </rioxxterms:publication_date>

becomes OpenAIRE property:

  <dc:date>
    2015
  </dc:date> 
rioxxterms:type
One or one
dc:type
One or more
This MUST be included. This must use the controlled vocabulary mapping specified below in the table called Vocabulary mapping: Publication Types
rioxxterms:version
One exactly
dc:relation
One exactly
This MUST be included. This must use the controlled vocabulary mapping specified below in the table called Vocabulary mapping: Publication Versions
rioxxterms:version_of_record
Zero or one
dc:relation
Zero or more
This MUST be included, if available. If provided in the RIOXX record, value will be in the form of an HTTP URI

Vocabulary mapping: Publication Types

RIOXXOpenAIRENotes
Bookinfo:eu-repo/semantics/book
Book Chapterinfo:eu-repo/semantics/bookPart
Conference Paper/Proceeding/Abstractinfo:eu-repo/semantics/conferenceObject
Journal Article/Reviewinfo:eu-repo/semantics/article
Manual/Guideinfo:eu-repo/semantics/technicalDocumentation
Monographinfo:eu-repo/semantics/book
Policy Briefing Reportinfo:eu-repo/semantics/report
Technical Reportinfo:eu-repo/semantics/report
Technical Standardinfo:eu-repo/semantics/other
Thesisinfo:eu-repo/semantics/otherOpenAIRE provides:

  • info:eu-repo/semantics/bachelorThesis
  • info:eu-repo/semantics/masterThesis
  • info:eu-repo/semantics/doctoralThesis

but since it is impossible to select from these based on the RIOXX term, it would be potentially misleading to use one of these OpenAIRE terms

Otherinfo:eu-repo/semantics/other
Consultancy Reportinfo:eu-repo/semantics/report
Working Paperinfo:eu-repo/semantics/workingPaper

Vocabulary mapping: Publication Versions

RIOXXOpenAIRENotes
**AO** = Author's Originalinfo:eu-repo/semantics/authorVersion
**SMUR** = Submitted Manuscript Under Reviewinfo:eu-repo/semantics/submittedVersion
**AM** = Accepted Manuscriptinfo:eu-repo/semantics/acceptedVersion
**P** = ProofThere is no eqivalent OpenAIRE term for this.
**VoR** = Version of Recordinfo:eu-repo/semantics/publishedVersion
**CVoR** = Corrected Version of Recordinfo:eu-repo/semantics/updatedVersion
**EVoR** = Enhanced Version of Recordinfo:eu-repo/semantics/updatedVersion
**NA** = Not Applicable (or Unknown)info:eu-repo/semantics/updatedVersion

Designed by Paul Walk, built with  Hugo
Copyright © EDINA. This website and blog are licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License