Create rioxx3.xsl

[jesusbagpuss]

In the screen branch there is a n00b XSL just as an example to render in the screen.

Plans for the XSL:

• [ ] Allow XSL to be <xsl:import href="rioxx3.xsl"/>ed into oai2.xsl
• [x] Use XSL to render info on the EPrints::View::RIOXX3 screen
• [ ] Create human readable mappings for COAR vocabs
• [ ] Create advice text for required/should fields, where the data is missing
• [ ] Check namespaces
• [ ] Share with non-EPrints community!?

COAR vocabs:

• Access rights - see also the DSpace phrase file
• Resource types - and DSpace phrase v3.1.
• Version types - DSpace phrases

Possible approach to mapping in XSL:

<!-- remember to define xmlns:coar="coar" exclude-result-prefixes="coar" in stylesheet declaration! -->
<xsl:variable name="coar-access-rights" select="document('')//coar:access_rights"/>

<coar:access_rights>
  <coar:lookup uri="c_ab4af688f83e57aa" label="AM">
    <desc>The version of a resource that has been accepted for publication. A second party takes permanent responsibility for the resource. Content and layout follow publisher’s submission requirements.</desc>
  </coar:lookup>
  ...
</coar:access_rights>

<xsl:template match="###???###">
    <xsl:variable name="value_to_lookup" select="### last-part of the COAR attribute value###"/>
    <xsl:value-of select='$coar-access-rights/coar:lookup[@uri = $value_to_lookup]/@label'/>
</xsl:template>

[drn05r]

Does this mappings include mappings from IDs for licences currently in the licenses namedset to be mapped to resolvable URIs for those licences. What should we do for IDs that do not have a sensible mapping? I assume we do a bit of a hack like RIOXX2 (e.g. https://www.rioxx.net/licenses/all-rights-reserved/) but in this case we would have to create URLs on the repo rather than a centralised point. Maybe we should have a set of mappings with the plugin for obvious values (e.g. cc_by_nc and anything that does not map automatically gets put under https://HOSTNAME/licenses/LICENSE_ID/