Skip to content

In DataCite/Datacite export, when the user enters a Keyword Term URI, include Keyword Term URI in the valueURI property of the subject property #12300

Description

@jggautier

Overview of the Feature Request

When the user enters a Keyword Term URI, the DataCite/Datacite export should include the Keyword Term URI in the valueURI property of the subject property, as the OpenAIRE/oai_datacite export already does. Currently, the DataCite/Datacite export excludes the Keyword Term URI from the valueURI property.

This issue is part of a larger effort to align both metadata exports, described in #11916 and #12281. @qqmyers worked on this change in his PR at #12346. When merged, that PR will mark this issue as done.

What kind of user is the feature intended for?

API User, Superuser, and Sysadmin

What inspired the request?

This is part of a larger effort to align the OpenAIRE/oai_datacite and DataCite/Datacite metadata exports. There is more context at #11916 and #12281.

What existing behavior do you want changed?

Currently, the DataCite/Datacite export doesn't include a valueURI property with the Keyword Term URI. For example:

<subject
    schemeURI="https://controlledvocabularyurl1.org"
    subjectScheme="Keyword Vocab Name 1">Keyword Term 1
</subject>

<subject>Keyword Term 2</subject>

The OpenAIRE/oai_datacite export includes the Keyword Term URI in the valueURI property. For example:

<subject
    schemeURI="https://controlledvocabularyurl1.org"
    valueURI="https://keywordtermuri1.org"
    subjectScheme="Keyword Vocab Name 1">Keyword Term 1
</subject>

<subject
    valueURI="https://keywordtermuri2.org">Keyword Term 2
</subject>

The DataCite/Datacite export should be changed to include the Keyword Term URI in the valueURI property in the same way that the OpenAIRE/oai_datacite export does.

Any open or closed issues related to this feature request?

Metadata

Metadata

Assignees

No one assigned

    Labels

    GREI 3Search and BrowseSize: 3A percentage of a sprint. 2.1 hours.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions