Rioxx 3.0

This is the current version of the application profile
see other versions

Terminology

the primary resource refers to the thing being described by the Rioxx record.

the resource refers to resources that are not the primary resource. A resource can encompass resource identifiers (i.e. URIs), such as persistent identifiers.

landing page refers to an entry page on a repository or publication platform that describes the primary resource and provides links to related resources.

custodianship refers to the concept that the location of a primary resource and a resource is significant to understanding the nature of the thing being described by the Rioxx record and is relevant to machine processing of Rioxx metadata. Resources under direct custodianship are those which are under direct management of a local repository or publication platform, and under which that local system controls and maintains file content and/or other resources. Resources outside this direct custodianship (e.g. resources at or hosted by third party services) demonstrate external custodianship.

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.

Properties in this profile

dc:coverage | dc:description | dc:identifier | dc:language | dc:relation | dc:source | dc:subject | dc:title | dc:type | dcterms:dateAccepted | rioxxterms:contributor | rioxxterms:creator | rioxxterms:ext_relation | rioxxterms:grant | rioxxterms:id | rioxxterms:name | rioxxterms:project | rioxxterms:publication_date | rioxxterms:publisher | rioxxterms:record_public_release_date

Example Rioxx Records

Some examples of full Rioxx records (serialised as XML) are provided at the bottom of this page

Property details and examples

Element Cardinality Description
dc:coverage Zero or more

Coverage (dc:coverage) will typically include a temporal period (a period label, date, or date range) or jurisdiction (such as a named administrative entity).
dc:description Zero or more

The purpose of dc:description is to describe the content of the primary resource using free text. It is RECOMMENDED that an English language abstract be used where available. HTML or other markup tags SHOULD NOT be included in this field. This field may be indexed and its contents presented to people conducting searches.
dc:identifier Exactly one

dc:identifier MUST contain an identifying HTTP(S) URI of the repository 'landing page' describing this resource. The landing page should provide links to related resources. We RECOMMEND using FAIR Signposting (signposting.org/FAIR) to assist machine agents in navigating from the landing page to the relevant resources. The value of dc:identifier does not have to be a persistent identifier (PID), instead, in order to facilitate indexing by machine agents. It is RECOMMENDED that dc:identifier contains a direct HTTP(S) URI of the landing page, i.e. resolving dc:identifier SHOULD be possible without the use of HTTP redirection.

Example

A typical example of this property is provided below, where the direct HTTP(S) URI of the repository landing page is expressed.

<dc:identifier>https://www.repository.cam.ac.uk/items/c6173013-1e2f-4818-9d1e-98a0f189c7c8</dc:identifier>

dc:identifier can be supplemented by using dc:relation to declare the local repository PID for the corresponding resource, in this case a DOI.

<dc:relation rel="cite-as">https://doi.org/10.17863/CAM.101562</dc:relation>
dc:language One or more

This refers to the primary language in which the content of the primary resource is presented. The property MAY be repeated if the resource contains multiple languages. Values used for this property MUST conform to ISO 639-3. This offers two and three letter tags e.g. "en" or "eng" for English and "en-GB" for English used in the UK.
dc:relation Zero or more

Although this property is not strictly mandated in the Rioxx schema, it SHOULD be included because this is the property which harvesting software will inspect to locate URLs for resource file content - for example to locate the "full text" associated with a repository record. It will also be the property to declare a persistent identifier (PID) that may be associated with the resource.

Note that only those resources under the direct custodianship of the repository should be asserted within dc:relation. Resources demonstrating external custodianship should be related using rioxxterms:ext_relation.

dc:relation is refined by a series of attributes, which SHOULD be included (where applicable):

  • rel
  • type
  • coar_type
  • coar_version
  • deposit_date
  • resource_exposed_date
  • access_rights
  • license_ref

When set to rel="item", the dc:relation property identifies a downloadable resource. Each such dc:relation property MUST contain an HTTP(S) URI resolving to the downloadable resource. It is REQUIRED that this property is used whenever the Rioxx record identifies a downloadable object under the direct custodianship of the repository, such as a full text, dataset or software. Where such deposited downloadable resource remains under a temporary embargo, the repository SHOULD return an appropriate HTTP status code to indicate that access to the resource is forbidden, until the embargo's expiry. The most appropriate HTTP code to return is 451 Unavailable For Legal Reasons.

When set to rel="cite-as", the dc:relation property specifies a cite-able identifier associated with the resource.

dc:relation MUST only be used to identify resources under the direct custodianship of the repository, therefore all URIs specified under dc:relation MUST resolve to the repository. URIs identifying related resources that resolve to resources outside of the direct custodianship of the repository MUST be specified under rioxxterms:ext_relation.

The dc:relation property can be repeated to specify more than one associated resource. Possible values here may include a DOI, URN, CORE OAI ID; or an alternative repository HTTP(S) URI where there is no requirement for a PID.

Attributes

  1. rel: The rel attribute uses 'typed links' from the IANA Link Relation Registry. This attribute will often be set to rel='item' where dc:relation is being used to communicate downloadable file content, but will be set to rel="cite-as" where dc:relation is simulataneously being used to declare an associated persistent identifier.
  2. type: The type attribute refers to the technical format of the value of dc:relation. When used, type MUST encode the Media Type of the resource (formerly MIME Type). Note that this attribute should not be confused with coar_type.
  3. coar_type: When used, the coar_type attribute MUST contain a value which is an identifier from the COAR Resource Types Vocabulary. For example, for the common case of the resource being a PDF of a journal article, the RECOMMENDED value would be http://purl.org/coar/resource_type/c_6501 ('journal article'). The COAR Resource Types Vocabulary accommodates a diverse range of resource types. dc:relation can therefore also be used to communicate the existence of directly harvestable related data or software, such as by types experimental data or research software.
  4. coar_version: When used, the coar_version attribute MUST contain a value which is an identifier from the COAR Version Types Vocabulary.
  5. deposit_date: The deposit_date attribute (if present) takes the date on which this resource was first deposited, irrespective of any relevant embargoes or dark archiving, and irrespective of any subsequent file replacement(s). It is anticipated that in some circumstances the deposit_date will be captured and exposed in repository metadata when the resource described is under temporary embargo or temporary dark archiving. If included, this attribute's value MUST be encoded according to the W3CDTF (a profile of ISO 8601) which typically follows the following format: YYYY-MM-DD.
  6. resource_exposed_date: The resource_exposed_date attribute (if present) takes the date on which this related resource was made publicly available, irrespective of any subsequent file replacement(s). If included, this attribute's value MUST be encoded according to the W3CDTF (a profile of ISO 8601) which typically follows the following format: YYYY-MM-DD. Repositories will typically fulfil resource_exposed_date if the related resource is made publicly visible immediately upon deposit, or when an applicable embargo ends.
  7. access_rights: When used, the access_rights attribute MUST take a URI value from the COAR Access Rights Vocabulary, which defines four access states: embargoed access, metadata only access, open access, restricted access.
  8. license_ref: When used, the license_ref attribute MUST communicate the license terms under which the value of dc:relation is subject using an HTTP(S) URI. Typical examples might include the variety of licenses made available by Creative Commons, but can conceivably include any license referencible by URI.

Examples

Example 1:

A typical dc:relation property may resemble this example, in which the property value is the downloadable resource:

<dc:relation 
    rel="item"
    type="application/pdf"
    coar_type="https://purl.org/coar/resource_type/c_6501" 
    coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
    deposit_date="2023-03-28" 
    resource_exposed_date="2023-03-28" 
    access_rights="https://purl.org/coar/access_right/c_abf2"
    license_ref="https://creativecommons.org/licenses/by/4.0/">
            https://strathprints.strath.ac.uk/84907/7/Jiang_etal_IEEETGRS_2023_Microseismic_event_classification.pdf
</dc:relation>

Example 2:

Example 1 can be elaborated to declare the local repository PID associated with the downloadable resource, in this case a DOI:

<dc:relation 
    rel="item"
    type="application/pdf"
    coar_type="https://purl.org/coar/resource_type/c_6501" 
    coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
    deposit_date="2023-03-28" 
    resource_exposed_date="2023-04-11" 
    access_rights="https://purl.org/coar/access_right/c_abf2"
    license_ref="https://creativecommons.org/licenses/by/4.0/">
            https://strathprints.strath.ac.uk/84907/7/Jiang_etal_IEEETGRS_2023_Microseismic_event_classification.pdf
</dc:relation>

<dc:relation rel="cite-as">https://doi.org/10.17868/strath.00084907</dc:relation>

Example 3:

The dc:relation property can be repeated to communicate the existence of more than one downloadable resource, including other instances (or 'expressions') providing they are within the direct custodianship of the local repository.

This example describes two downloadable resources (journal article and associated research instrument). It also includes the declaration of a repository PID associated with resources.

<dc:relation 
    rel="item"
    type="application/pdf"
    coar_type="https://purl.org/coar/resource_type/c_6501" 
    coar_version="https://purl.org/coar/version/c_970fb48d4fbd8a85"
    deposit_date="2023-10-18" 
    resource_exposed_date="2023-10-18" 
    access_rights="https://purl.org/coar/access_right/c_abf2"
    license_ref="https://creativecommons.org/licenses/by/4.0/">
            https://eprints.whiterose.ac.uk/204315/1/amt-16-4375-2023.pdf
</dc:relation>

<dc:relation 
    rel="item"
    type="application/pdf"
    coar_type="http://purl.org/coar/resource_type/YZ1N-ZFT9" 
    deposit_date="2023-10-18" 
    resource_exposed_date="2023-10-18" 
    access_rights="https://purl.org/coar/access_right/c_abf2"
    license_ref="https://creativecommons.org/licenses/by/4.0/">
             https://eprints.whiterose.ac.uk/204315/9/amt-16-4375-2023-supplement.pdf
</dc:relation>

<dc:relation rel="cite-as">https://oai.core.ac.uk/oai:eprints.whiterose.ac.uk:204315</dc:relation>
dc:source Zero or one

The dc:source property describes the source from which the primary resource is derived (in whole or in part). It is RECOMMENDED that the source is referenced using a unique identifier from a recognised system e.g. the unique 8-digit International Standard Serial Numbers (ISSN) assigned to electronic periodicals, or the 13 digit International Standard Book Number (ISBN13) assigned to books. In the latter case, the ISBN13 for the electronic version of the book SHOULD be used if available.

Use of this property is applicable where the primary resource is to be published as part of a larger resource. Typical examples might include a conference paper belonging to proceedings or a chapter of a book (but not a complete book).
dc:subject Zero or more

dc:subject is used to describe the subject of the primary resource. It is RECOMMENDED that a URI be used for the value, however a literal value that identifies the subject may be provided instead. Both should preferably refer to a subject in a controlled vocabulary.
dc:title Exactly one

This refers to the title, and any sub-titles, of the primary resource. The title should be represented using the original spelling and wording. The RECOMMENDED format for expressing subtitles is:

Title: Subtitle

Note that where the primary resource is a chapter in a book, the chapter title MUST be entered here, with the ISBN13 of the book being recorded in the dc:source property.
dc:type One or more

Type refers to the nature or genre of the content of the primary resource. This property should not be confused with the type attribute in dc:relation.

The value recorded in dc:type MUST be an HTTP(S) URI taken from the COAR Controlled Vocabulary for Resource Type Genres, which provides a hierarchical model of resource type genres.

Example:

<dc:type>
    https://purl.org/coar/resource_type/c_5794
</dc:type>
dcterms:dateAccepted Zero or one

The date on which the primary resource was accepted for publication. Property content MUST be encoded according to the W3CDTF (a profile of ISO 8601) which typically follows the following format: YYYY-MM-DD.
rioxxterms:contributor Zero or more

The rioxxterms:contributor property describes the party responsible for making contributions to the content of the primary resource. This is normally a person, but may be an organisation or service.

Where available and possible, the RECOMMENDED format is to encode the name of the contributor within the sub-property rioxxterms:name, and to include a recognised identifier in its HTTP(S) URI form using the rioxxterms:id sub-property, e.g.

<rioxxterms:contributor>
	<rioxxterms:name>Bhopal, Kalwant</rioxxterms:name>
	<rioxxterms:id>https://orcid.org/0000-0003-3017-6595</rioxxterms:id>
</rioxxterms:contributor>

If necessary, multiple instances of rioxxterms:id may be included to communicate additional identifier schemes, e.g.

<rioxxterms:contributor>
	<rioxxterms:name>Bhopal, Kalwant</rioxxterms:name>
	<rioxxterms:id>https://orcid.org/0000-0003-3017-6595</rioxxterms:id>
	<rioxxterms:id>https://isni.org/isni/0000000038079210</rioxxterms:id>
	<rioxxterms:id>https://www.wikidata.org/wiki/Q61998297</rioxxterms:id>
</rioxxterms:contributor>

Where the contributor is an organisation, the RECOMMENDED format is to add the official name of the organisation as the content of rioxxterms:contributor and to include a recognised persistent identifier scheme in its HTTP(S) URI form within an instance of rioxxterms:id. Such an identifier scheme might include ISNI, Research Organization Registry, VIAF or WikiData concept URI, e.g.

<rioxxterms:contributor>
	<rioxxterms:name>Stanford University</rioxxterms:name>
	<rioxxterms:id>https://isni.org/isni/0000000419368956</rioxxterms:id>
</rioxxterms:contributor>
rioxxterms:creator One or more

The rioxxterms:creator property describes the party responsible for creating the primary resource. This is normally a person, but may be an organisation or service.

Where available and possible, the RECOMMENDED the name of the creator should be encoded within the rioxxterms:name sub-property, and to include a recognised identifier in its HTTP(S) URI form using the rioxxterms:id sub-property, e.g.

<rioxxterms:creator>
    <rioxxterms:name>Smith, Adam</rioxxterms:name>
    <rioxxterms:id>https://isni.org/isni/0000000122796642</rioxxterms:id>
</rioxxterms:creator>

If necessary, multiple instances of rioxxterms:id may be included to communicate additional identifier schemes, e.g.

<rioxxterms:creator>
    <rioxxterms:name>Fry, Hannah</rioxxterms:name>
    <rioxxterms:id>https://isni.org/isni/0000000446254946</rioxxterms:id>
    <rioxxterms:id>http://viaf.org/viaf/314908506</rioxxterms:id>
    <rioxxterms:id>https://orcid.org/0000-0003-0601-9100</rioxxterms:id>
</rioxxterms:creator>

Where an organisation requires attribution, the RECOMMENDED format is to add the official name of the organisation as the content of rioxxterms:creator, and to include a recognised persistent identifier scheme in its HTTP(S) URI form within rioxxterms:id. Such an identifier scheme might include ISNI, Research Organization Registry, VIAF or WikiData concept URI, e.g.

<rioxxterms:creator>
    <rioxxterms:name>C.E.R.N.</rioxxterms:name>
    <rioxxterms:id>https://isni.org/isni/000000012156142X</rioxxterms:id>
    <rioxxterms:id>https://ror.org/01ggx4157</rioxxterms:id>
</rioxxterms:creator>

Where the rioxxterms:creator property appears multiple times for one record, it CAN be assumed that the order is significant, in that the first element describes the first named author of the resource. In order to make this more explicit, an extra attribute, first-named-author, SHOULD be used to indicate which of the rioxxterms:creator elements describes the first named author of the resource, thus:

<rioxxterms:creator first-named-author="true">
    <rioxxterms:name>Olusoga, David</rioxxterms:name>
    <rioxxterms:id>https://isni.org/isni/0000000096386112</rioxxterms:id>
</rioxxterms:creator>
rioxxterms:ext_relation Zero or more

rioxxterms:ext_relation is used to convey external associations to related resources (i.e. external relations). Such relational associations will be scholarly resources hosted externally, i.e. outside of the direct custodianship of the repository asserting the relational associations. Examples of these associations might typically include alternative 'expressions' of the primary resource (e.g. preprint, VoR, etc.) and/or resources relevant to understanding the primary resource, such as related research data, software, code, instruments, and so forth. Where such types have been encoded it will be considered to be for the purposes of contributing to the scholarly data graph and/or end users, rather than for assisting harvesting software in locating file content, such as full text, which is instead conveyed via dc:relation property.

Each external relation MUST appear as a separate instance of the rioxxterms:ext_relation property.

rioxxterms:ext_relation MUST include the rel and coar_type attributes. The coar_version attribute MAY be included (where appropriate), if the related resource is a publication.

  1. rel: The rel attribute uses 'typed links' from the IANA Link Relation Registry. As Rioxx uses rioxxterms:ext_relation to communicate external associations, this attribute will normally be set to "cite-as", e.g. rel='cite-as' when the rioxxterms:ext_relation conveys a related PID resolving to an external resource or rel='item' when rioxxterms:ext_relation identifies a downloadable external resource.

  2. coar_type: The coar_type attribute MUST contain an identifier from the COAR Resource Types Vocabulary. For example, for the common case of the related resource being a PDF of a journal article, the RECOMMENDED value would be http://purl.org/coar/resource_type/c_6501. The COAR Resource Types Vocabulary accommodates a diverse range of resource types.

  3. coar_version: The coar_version attribute SHOULD be included if rioxxterms:ext_relation is being used to indicate an associative relation with an alternative instance of the the primnary resource, where the resource is a publication. Where this is true coar_version MUST contain an identifier value from the COAR Version Types Vocabulary.

Examples:

Related published article

<rioxxterms:ext_relation 
    rel="cite-as"
    coar_type="https://purl.org/coar/resource_type/c_6501" 
    coar_version="https://purl.org/coar/version/c_970fb48d4fbd8a85">
            https://doi.org/10.1007/s11229-020-02724-x
</rioxxterms:ext_relation>

Related dataset

<rioxxterms:ext_relation 
    rel="cite-as"            
    coar_type="https://purl.org/coar/resource_type/c_ddb1">
            https://doi.org/10.15129/589f7af3-26b3-4a93-b042-fbc8100fc977
</rioxxterms:ext_relation>
rioxxterms:grant Zero or more

The purpose of rioxxterms:grant is to collect grant ID(s), issued by the relevant funder(s), that relate to the primnary resource being described, together with the name and/or global identifier for the funder(s).

The property MUST contain one grant ID. A grant ID can take the form of any identifier provided by the funder, preferably represented as an HTTP(S) URI. In cases where the primnary resource has been funded internally, an appropriate internal code might be used.

The property takes two attributes: funder_name and funder_id. One or both of funder_name and funder_id MUST be supplied.

funder_name

The canonical name of the entity responsible for funding the primary resource SHOULD be recorded here as text.

funder_id

A globally unique identifier for the funder of the primary resource SHOULD be recorded here. An HTTP(S) URI MUST be used for this. It is RECOMMENDED that one of the following identifier schemes is used:

Examples

<rioxxterms:grant
    funder_name="Wellcome Trust"
    funder_id="https://isni.org/isni/0000000404277672">
    https://doi.org/10.35802/218671
</rioxxterms:grant>

or

<rioxxterms:grant
    funder_name="Arts and Humanities Research Council"
    funder_id="https://ror.org/0505m1554">
    AH/W007622/1
</rioxxterms:grant>

Where the primary resource has been funded by more than one funder a separate rioxxterms:grant property can be added for each. Similarly, where several grant IDs provided by the same funder have been attached to the primary resource, a separate rioxxterms:grant property can be added for each.

This means that it is permissible for a given funder_name or funder_id to appear in multiple instances of the rioxxterms:grant property in a single Rioxx metadata record.
rioxxterms:id n/a

The rioxxterms:id property MUST NOT be used directly in the root of a Rioxx record, but MAY be used to add identifiers into the following root properties:

  • rioxxterms:contributor
  • rioxxterms:creator
  • rioxxterms:publisher

Identifiers represented by the rioxxterms:id property MUST be HTTP(S) URIs.
rioxxterms:name n/a

The rioxxterms:name property MUST NOT be used directly in the root of a Rioxx record, but MAY be used to add a name into the following root properties:

  • rioxxterms:contributor
  • rioxxterms:creator
  • rioxxterms:publisher
rioxxterms:project Zero or more

The purpose of rioxxterms:project is to collect project ID(s), that relate to the resource.

When present, the rioxxterms:project property MUST contain one project ID, a globally unique persistent identifier that identifies a project. Examples might include:

Example

<rioxxterms:project>
    https://handle.net/10378.1/1590366
</rioxxterms:project>

Where the resource is associated with more than one project ID, a rioxxterms:project property can be added for each. This means that it is permissible for multiple instances of the rioxxterms:project property to appear in a single Rioxx metadata record.
rioxxterms:publication_date Zero or one

This property takes the publication date of the primary resource in the form in which it would be cited. This allows a Rioxx record to function as a reasonable bibliographic record for the primary resource.

Where possible the property's value' SHOULD be encoded according to the W3CDTF (a profile of ISO 8601) which typically follows the following format: YYYY-MM-DD.

Example:

<rioxxterms:publication_date>
    2011-02-23
</rioxxterms:publication_date>

It is acknowledged that the publication date conventions of certain publishers vary, making the identification of precise publication dates problematic, especially in instances where a publisher assigns a resource to a seasonal issue date, e.g. "Spring 2020", "Winter 2019", etc. To maintain adherence to the above noted encoding conventions, resources with publication dates assigned to seasonal issues should be expressed according to the following convention, with months expressed as per:

  • 01 = winter (beginning of year)
  • 04 = spring
  • 07 = summer
  • 10 = autumn
  • 12 = winter (end of year)

Examples:

Spring 2020

<rioxxterms:publication_date>
    2020-04
</rioxxterms:publication_date>

Winter 2019 (end of year)

<rioxxterms:publication_date>
    2019-12
</rioxxterms:publication_date>
rioxxterms:publisher Zero or more

This property contains the name of the entity, typically a publisher, responsible for making the version of record of the primary resource available. This could be a person, organisation or service.

Where available and possible, the RECOMMENDED format is to add the official name of the publisher as the content of the property, and to include one or more recognised identifiers in their HTTP(S) URI form using child rioxxterms:id properties, e.g.

<rioxxterms:publisher>
    <rioxxterms:name>Public Library of Science</rioxxterms:name>
    <rioxxterms:id>https://isni.org/isni/000000040482455X</rioxxterms:id>
    <rioxxterms:id>https://isni.org/isni/0000000404826432</rioxxterms:id>
</rioxxterms:publisher>

<rioxxterms:publisher>
    <rioxxterms:name>Ubiquity Press (United Kingdom)</rioxxterms:name>
    <rioxxterms:id>https://ror.org/00qpqrv96</rioxxterms:id>
</rioxxterms:publisher>

Typical identifier schemes likely to be relevant here include ISNI, ROR, and VIAF.
rioxxterms:record_public_release_date Zero or one

This property takes the date upon which metadata about the primary resource being described was first made publicly visible. Property content MUST be encoded according to the W3CDTF (a profile of ISO 8601) which typically follows the following format: YYYY-MM-DD.

Examples:

<rioxxterms:record_public_release_date>
    2020-10-02
</rioxxterms:record_public_release_date>

or

<rioxxterms:record_public_release_date>
    2020-09-29T19:20+01:00
</rioxxterms:record_public_release_date>

It is accepted that in some circumstances rioxxterms:record_public_release_date will be captured and exposed in repository metadata prior to the availability of related resources such as the "full text" for a publication; for example as the result of a delay in depositing the full text, or where it is under temporary embargo or temporary dark archiving.

Example Rioxx Records (XML)

<?xml version='1.0' encoding='UTF-8'?>
<rioxx xsi:schemaLocation="http://www.rioxx.net/schema/v3.0/rioxx/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rioxxterms="http://docs.rioxx.net/schema/v3.0/rioxxterms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dc:description>The kinematic lower bound for the single scattering of neutrons produced in deuterium-tritium (DT) fusion reactions produces a backscatter edge in the measured neutron spectrum. The energy spectrum of backscattered neutrons is dependent on the scattering ion velocity distribution. As the neutrons preferentially scatter in the densest regions of the capsule, the neutron backscatter edge presents a unique measurement of the hydrodynamic conditions in the dense DT fuel. It is shown that the spectral shape of the edge is determined by the scattering rate weighted fluid velocity and temperature of the dense DT fuel layer during neutron production. In order to fit the neutron spectrum, a model for the various backgrounds around the backscatter edge is developed and tested on synthetic data produced from hydrodynamic simulations of OMEGA implosions. It is determined that the analysis could be utilized on current inertial confinement fusion experiments in order to measure the dense fuel properties.</dc:description>
    
    <dc:language>en</dc:language>
    
    <dc:source>1070-664X</dc:source>
    
    <dc:title>Neutron backscatter edge: A measure of the hydrodynamic properties of the dense DT fuel at stagnation in ICF experiments</dc:title>
    
    <dcterms:dateAccepted>2019-12-01</dcterms:dateAccepted>

    <rioxxterms:creator
            first-named-author="true">
        <rioxxterms:name>Crilly, A. J.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-0429-9332</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Appelbe, B. D.</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Mannion, O. M.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0001-8029-5109</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Forrest, C. J.</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Gopalaswamy, V.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-8013-9314</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Walsh, C. A.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-6639-3543</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Chittenden, J. P.</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:publication_date>2020-01-03</rioxxterms:publication_date>
   
    <rioxxterms:publisher>
        <rioxxterms:name>AIP</rioxxterms:name>
        <rioxxterms:id>https://isni.org/isni/0000000405564665"</rioxxterms:id>
    </rioxxterms:publisher>
    
    <rioxxterms:record_public_release_date>2020-01-20</rioxxterms:record_public_release_date>
    
    <dc:type>http://purl.org/coar/resource_type/c_2df8fbb1</dc:type>

    <rioxxterms:grant
            funder_name="Engineering and Physical Sciences Research Council"
            funder_id="https://ror.org/0439y7842">
        EP/P010288/1
    </rioxxterms:grant>
    
    <rioxxterms:grant
            funder_name="Lawrence Livermore National Laboratory"
            funder_id="https://ror.org/041nk4h53">
        B618573
    </rioxxterms:grant>

    <dc:identifier>https://spiral.imperial.ac.uk/handle/10044/1/76123</dc:identifier>

    <dc:relation
            rel="item"
            type="application/pdf"
            coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            deposit_date="2010-01-20"
            resource_exposed_date="2020-01-20"
            access_rights="https://purl.org/coar/access_right/c_abf2"
            license_ref="https://creativecommons.org/licenses/by-nc-nd/4.0">
            https://spiral.imperial.ac.uk/bitstream/10044/1/76123/2/POP19-AR-58732_accepted.pdf
    </dc:relation>

    <dc:relation rel="cite-as">http://hdl.handle.net/10044/1/76123</dc:relation>
    
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="http://purl.org/coar/resource_type/c_6501"
            coar_version="http://purl.org/coar/version/c_970fb48d4fbd8a8">
        https://doi.org/10.1063/1.5128830
    </rioxxterms:ext_relation>
</rioxx>


<?xml version='1.0' encoding='UTF-8'?>
<rioxx xsi:schemaLocation="http://www.rioxx.net/schema/v3.0/rioxx/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rioxxterms="http://docs.rioxx.net/schema/v3.0/rioxxterms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dc:description>Passive seismics help us understand subsurface processes, e.g. landslides, mining, geothermal systems etc. and help predict and mitigate their effects. Continuous monitoring results in long seismic records that may contain various sources, which need to be classified. Manual detection and labeling of recorded seismic events is not only time consuming but can also be inconsistent when done manually, even in the case where it is done by the same expert. Therefore, an automated approach for classification of continuous microseismic recordings based on a Convolutional Neural Network (CNN) is proposed, with a multiclassifier architecture that classifies earthquakes, rockfalls and low signal to noise ratio quakes. Furthermore, we propose three CNN architectures that take as input time series data, Short Time Fourier Transform (STFT) and Continuous Wavelet Transform (CWT) maps. The suitability of these three networks is rigorously assessed over five months of continuous seismometer recordings from the active Super-Sauze landslide in France. We observe that all three architectures have excellent and very similar performance. Furthermore, we evaluate transferability to a geographically distinct seismically active site in Larissa, Greece. We demonstrate that the proposed network is able to detect all 86 catalogued earthquake events, having only been trained on the Super-Sauze dataset and shows good agreement with manually detected events. This is promising as it could replace painstaking manual labelling of events in large recordings..</dc:description>
    
    <dc:language>en</dc:language>
    
    <rioxxterms:publisher>
        <rioxxterms:name>IEEE</rioxxterms:name>
        <rioxxterms:id>https://isni.org/isni/0000000121063391"</rioxxterms:id>
    </rioxxterms:publisher>
    
    <dc:source>0196-2892</dc:source>
    
    <dc:title>Microseismic event classification with time, frequency and wavelet domain convolutional neural networks</dc:title>
    
    <dcterms:dateAccepted>2023-03-17</dcterms:dateAccepted>

    <rioxxterms:creator
            first-named-author="true">
        <rioxxterms:name>Jiang, Jiaxin</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Stankovic, Vladimir</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-1075-2420</rioxxterms:id>
        <rioxxterms:id>https://isni.org/isni/0000000124141121</rioxxterms:id>
        <rioxxterms:id>https://viaf.org/viaf/667151246513444130519</rioxxterms:id>
        <rioxxterms:id>https://www.wikidata.org/wiki/Q51802269</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Stankovic, Lina</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-8112-1976</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Parastatidis, Emmanouil</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0001-5066-6917</rioxxterms:id>
        <rioxxterms:id>https://isni.org/isni/0000000493517163</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Pytharouli, Stella</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-2899-1518</rioxxterms:id>
        <rioxxterms:id>https://isni.org/isni/0000000351891635</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Miras, Haralampos N.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-0086-5173</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Cronin, Leroy</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0001-8035-5757</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:publication_date>2023-03-27</rioxxterms:publication_date>
    <rioxxterms:record_public_release_date>2023-03-28</rioxxterms:record_public_release_date>
    <dc:type>https://purl.org/coar/resource_type/c_2df8fbb1</dc:type>
    <rioxxterms:grant
            funder_name="Engineering and Physical Sciences Research Council"
            funder_id="https://ror.org/0439y7842">
        EP/S005560/1
    </rioxxterms:grant>
    <rioxxterms:project>https://handle.net/10378.1/1590366</rioxxterms:project>
    <dc:identifier>https://strathprints.strath.ac.uk/84907/</dc:identifier>

    <dc:relation
            rel="item"
            type="application/pdf"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
            deposit_date="2023-03-28"
            resource_exposed_date="2023-03-28"
            access_rights="https://purl.org/coar/access_right/c_abf2"
            license_ref="https://creativecommons.org/licenses/by/4.0/">
        https://strathprints.strath.ac.uk/84907/7/Jiang_etal_IEEETGRS_2023_Microseismic_event_classification.pdf
    </dc:relation>
    
    <dc:relation rel="cite_as">https://doi.org/10.17868/strath.00084907"</dc:relation>

    <!-- Other expressions - publisher version -->
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            coar_version="https://purl.org/coar/version/c_970fb48d4fbd8a85">
        https://doi.org/10.1109/TGRS.2023.3262412
    </rioxxterms:ext_relation>

    <!-- related  dataset -->
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_ddb1">
        https://doi.org/10.15129/589f7af3-26b3-4a93-b042-fbc8100fc977
    </rioxxterms:ext_relation>
</rioxx>


<?xml version='1.0' encoding='UTF-8'?>
<rioxx xsi:schemaLocation="http://www.rioxx.net/schema/v3.0/rioxx/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rioxxterms="http://docs.rioxx.net/schema/v3.0/rioxxterms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dc:description>YouTube has been implicated in the transformation of users into extremists and conspiracy theorists. The alleged mechanism for this radicalizing process is YouTube’s recommender system, which is optimized to amplify and promote clips that users are likely to watch through to the end. YouTube optimizes for watch-through for economic reasons: people who watch a video through to the end are likely to then watch the next recommended video as well, which means that more advertisements can be served to them. This is a seemingly innocuous design choice, but it has a troubling side-effect. Critics of YouTube have alleged that the recommender system tends to recommend extremist content and conspiracy theories, as such videos are especially likely to capture and keep users’ attention. To date, the problem of radicalization via the YouTube recommender system has been a matter of speculation. The current study represents the first systematic, pre-registered attempt to establish whether and to what extent the recommender system tends to promote such content. We begin by contextualizing our study in the framework of technological seduction. Next, we explain our methodology. After that, we present our results, which are consistent with the radicalization hypothesis. Finally, we discuss our findings, as well as directions for future research and recommendations for users, industry, and policy-makers..</dc:description>
    
    <dc:language>en</dc:language>
    
    <rioxxterms:publisher>
        <rioxxterms:name>Springer</rioxxterms:name>
        <rioxxterms:id>https://isni.org/isni/0000000460111909</rioxxterms:id>
    </rioxxterms:publisher>
    
    <dc:source>0039-7857</dc:source>
    
    <dc:title>Technologically scaffolded atypical cognition: the case of YouTube’s recommender system</dc:title>
    
    <dcterms:dateAccepted>2020-05-27</dcterms:dateAccepted>

    <rioxxterms:creator
            first-named-author="true">
        <rioxxterms:name>Alfano, Mark</rioxxterms:name>
        <rioxxterms:id>https://viaf.org/viaf/8232163464412905680007</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Fard, Amir Ebrahimi</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Carter, J. Adam</rioxxterms:name>
        <rioxxterms:id>http://orcid.org/0000-0002-1222-8331</rioxxterms:id>
        <rioxxterms:id>https://isni.org/isni/0000000452130579</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Clutton, Peter</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Klein, Colin</rioxxterms:name>
    </rioxxterms:creator>

    <rioxxterms:publication_date>2021-12</rioxxterms:publication_date>
    
    <rioxxterms:record_public_release_date>2020-06-11</rioxxterms:record_public_release_date>
    
    <dc:type>https://purl.org/coar/resource_type/c_2df8fbb1</dc:type>
    
    <rioxxterms:grant
            funder_name="Australian Research Council"
            funder_id="https://ror.org/05mmh0f86">
        DP190101507
    </rioxxterms:grant>
    
    <rioxxterms:grant
            funder_name="John Templeton Foundation"
            funder_id="https://ror.org/035tnyy05">
        61387
    </rioxxterms:grant>

    <dc:identifier>https://eprints.gla.ac.uk/217807/</dc:identifier>

    <dc:relation
            rel="item"
            type="application/pdf"
            coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            deposit_date="2023-03-28"
            resource_exposed_date="2023-03-28"
            access_rights_="https://purl.org/coar/access_right/c_abf2"
            license_ref="https://creativecommons.org/licenses/by-nc-nd/4.0/"">
        https://eprints.gla.ac.uk/217807/7/217807.pdf
    </dc:relation>
    
    <dc:relation rel="cite-as">https://oai.core.ac.uk/oai:eprints.gla.ac.uk:217807</dc:relation>
    
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            coar_version="https://purl.org/coar/version/c_970fb48d4fbd8a85">
        https://doi.org/10.1007/s11229-020-02724-x
    </rioxxterms:ext_relation>

    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_ddb1">
        https://doi.org/10.15129/589f7af3-26b3-4a93-b042-fbc8100fc977
    </rioxxterms:ext_relation>
</rioxx>


<?xml version='1.0' encoding='UTF-8'?>
<rioxx xsi:schemaLocation="http://www.rioxx.net/schema/v3.0/rioxx/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:rioxxterms="http://docs.rioxx.net/schema/v3.0/rioxxterms/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <dc:description>Data on Secchi disc depth (the depth at which a standard white disc lowered into the water just becomes invisible to a surface observer) show that water clarity in the North Sea declined during the 20th century, with likely consequences for marine primary production. However, the causes of this trend remain unknown. Here we analyse the hypothesis that changes in the North Sea's wave climate were largely responsible by causing an increase in the concentrations of suspended particulate matter (SPM) in the water column through the resuspension of seabed sediments. First, we analysed the broad-scale statistical relationships between SPM and bed shear stress due to waves and tides. We used hindcasts of wave and current data to construct a space–time dataset of bed shear stress between 1997 and 2017 across the northwest European Continental Shelf and compared the results with satellite-derived SPM concentrations. Bed shear stress was found to drive most of the inter-annual variation in SPM in the hydrographically mixed waters of the central and southern North Sea. We then used a long-term wave reanalysis to construct a time series of bed shear stress from 1900 to 2010. This shows that bed shear stress increased significantly across much of the shelf during this period, with increases of over 20 % in the southeastern North Sea. An increase in bed shear stress of this magnitude would have resulted in a large reduction in water clarity. Wave-driven processes are rarely included in projections of climate change impacts on marine ecosystems, but our analysis indicates that this should be reconsidered for shelf sea regions.</dc:description>
    
    <dc:language>en</dc:language>
    
    <rioxxterms:publisher>
        <rioxxterms:name>European Geosciences Union</rioxxterms:name>
        <rioxxterms:id>https://isni.org/isni/0000000110927289</rioxxterms:id>
    </rioxxterms:publisher>
    
    <dc:source>1812-0792</dc:source>
    
    <dc:title>Increasing turbidity in the North Sea during the 20th century due to changing wave climate</dc:title>
    
    <dcterms:dateAccepted>2019-10-02</dcterms:dateAccepted>

    <rioxxterms:creator
            first-named-author="true">
        <rioxxterms:name>Wilson, Robert J.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0002-0592-366X</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:creator>
        <rioxxterms:name>Heath, Michael R.</rioxxterms:name>
        <rioxxterms:id>https://orcid.org/0000-0001-6602-3107</rioxxterms:id>
        <rioxxterms:id> https://viaf.org/viaf/15147423189944882613</rioxxterms:id>
    </rioxxterms:creator>

    <rioxxterms:publication_date>2019-12-09</rioxxterms:publication_date>
    
    <rioxxterms:record_public_release_date>2019-10-15</rioxxterms:record_public_release_date>
    
    <dc:type>https://purl.org/coar/resource_type/c_2df8fbb1</dc:type>
    
    <rioxxterms:grant
            funder_name="Australian Research Council"
            funder_id="https://ror.org/05mmh0f86">
        DP190101507
    </rioxxterms:grant>
    
    <rioxxterms:grant
            funder_name="John Templeton Foundation"
            funder_id="https://ror.org/035tnyy05">
        61387
    </rioxxterms:grant>

    <dc:identifier>https://strathprints.strath.ac.uk/70117/</dc:identifier>

    <dc:relation
            rel="item"
            type="application/pdf"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            coar_version="https://purl.org/coar/version/c_ab4af688f83e57aa"
            deposit_date="2019-12-11"
            resource_exposed_date="2019-12-11"
            access_rights_="https://purl.org/coar/access_right/c_abf2"
            license_ref="https://creativecommons.org/licenses/by-nc-nd/4.0/">
        https://strathprints.strath.ac.uk/70117/7/Wilson_Heath_OS2019_Increasing_turbidity_in_the_North_Sea_during_the_20th_century.pdf
    </dc:relation>

    <!-- Other expressions (or 'instances') - publisher version -->
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_6501"
            coar_version="https://purl.org/coar/version/c_970fb48d4fbd8a85">
        https://doi.org/10.1007/s11229-020-02724-x
    </rioxxterms:ext_relation>

    <!-- related  dataset -->
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/c_ddb1">
        https://doi.org/10.15129/5d28213e-8f9f-402a-b550-fc588518cb8b
    </rioxxterms:ext_relation >

    <!-- related software -->
    <rioxxterms:ext_relation
            rel="cite-as"
            coar_type="https://purl.org/coar/resource_type/QH80-2R4E">
        https://doi.org/10.5281/zenodo.3478185
    </rioxxterms:ext_relation>
</rioxx>