Hi,
while testing the plugin with OMP 3.5 and the ORCID Public API Sandbox, I found an issue with Crossref XML export.
Environment
- OMP 3.5.0-5
- OJSBR Crossref plugin for OMP 3.5
- ORCID integration configured with the Public Sandbox API
- Crossref XML schema 5.3.1
Steps to reproduce
- Configure ORCID in OMP using the ORCID Public Sandbox API.
- Authenticate an ORCID Sandbox account for a user.
- Submit and publish a monograph with this user as a contributor.
- Try to export the monograph from:
Settings → Distribution → DOIs → Export DOIs
Result
The export fails with:
An XML validation error occurred and the XML could not be exported.
As a control test, I removed the ORCID identifier from the contributor and exported exactly the same publication again. The XML export then succeeded.
It appears that OMP stores the authenticated sandbox identifier as:
https://sandbox.orcid.org/0000-....
and the Crossref plugin exports the value directly into the element.
However, the Crossref 5.3.1 schema accepts ORCID values matching:
https://orcid.org/0000-....
and therefore the sandbox URI fails schema validation.
This appears to affect testing rather than production ORCID identifiers, but it makes it difficult to test the full "ORCID Sandbox → OMP → Crossref XML" workflow.
Would it be possible either to handle Sandbox ORCID identifiers during Crossref export, or document this limitation for users testing the plugin?
I would be happy to provide additional test information if useful.
Hi,
while testing the plugin with OMP 3.5 and the ORCID Public API Sandbox, I found an issue with Crossref XML export.
Environment
Steps to reproduce
Settings → Distribution → DOIs → Export DOIs
Result
The export fails with:
As a control test, I removed the ORCID identifier from the contributor and exported exactly the same publication again. The XML export then succeeded.
It appears that OMP stores the authenticated sandbox identifier as:
https://sandbox.orcid.org/0000-....
and the Crossref plugin exports the value directly into the element.
However, the Crossref 5.3.1 schema accepts ORCID values matching:
https://orcid.org/0000-....
and therefore the sandbox URI fails schema validation.
This appears to affect testing rather than production ORCID identifiers, but it makes it difficult to test the full "ORCID Sandbox → OMP → Crossref XML" workflow.
Would it be possible either to handle Sandbox ORCID identifiers during Crossref export, or document this limitation for users testing the plugin?
I would be happy to provide additional test information if useful.