Overview of the Feature Request
When the user chooses PURL from the Related Publication Identifier Type dropdown, the OpenAIRE/oai_datacite export should use the value the user enters as the related identifier, as the DataCite/Datacite export already does. Currently, the OpenAIRE/oai_datacite export uses "https://purl.org" as the related identifier instead of the value the user entered.
This issue is part of a larger effort to align both metadata exports, described in #11916 and #12281.
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 uses the value the user entered as the related identifier when the user chooses PURL from the Related Publication Identifier Type dropdown. For example:
<relatedIdentifier
relationType="IsCitedBy"
relatedIdentifierType="PURL">12345
</relatedIdentifier>The OpenAIRE/oai_datacite export uses "https://purl.org" as the related identifier instead of the value the user entered. For example:
<relatedIdentifier
relationType="IsCitedBy"
relatedIdentifierType="PURL">https://purl.org
</relatedIdentifier>The OpenAIRE/oai_datacite export should be changed to use the value the user entered as the related identifier when the user chooses PURL as the identifier type, matching the behavior of the DataCite/Datacite export.
Any open or closed issues related to this feature request?
Overview of the Feature Request
When the user chooses PURL from the Related Publication Identifier Type dropdown, the OpenAIRE/oai_datacite export should use the value the user enters as the related identifier, as the DataCite/Datacite export already does. Currently, the OpenAIRE/oai_datacite export uses "https://purl.org" as the related identifier instead of the value the user entered.
This issue is part of a larger effort to align both metadata exports, described in #11916 and #12281.
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 uses the value the user entered as the related identifier when the user chooses PURL from the Related Publication Identifier Type dropdown. For example:
The OpenAIRE/oai_datacite export uses "https://purl.org" as the related identifier instead of the value the user entered. For example:
The OpenAIRE/oai_datacite export should be changed to use the value the user entered as the related identifier when the user chooses PURL as the identifier type, matching the behavior of the DataCite/Datacite export.
Any open or closed issues related to this feature request?