Skip to content

Fix double-escaped directApiCall URL in OAI-PMH metadata - #12684

Open
igorzelaya-io wants to merge 1 commit into
IQSS:developfrom
igorzelaya-io:fix-12670-oai-direct-api-url
Open

Fix double-escaped directApiCall URL in OAI-PMH metadata#12684
igorzelaya-io wants to merge 1 commit into
IQSS:developfrom
igorzelaya-io:fix-12670-oai-direct-api-url

Conversation

@igorzelaya-io

Copy link
Copy Markdown

Fixes #12670

Summary

  • stop pre-escaping the query separator before XOAI serializes the directApiCall XML attribute
  • add integration coverage that parses the OAI-PMH response and verifies the resulting export URL

Verification

  • reproduced the regression on Demo Dataverse 6.11: the raw attribute contains &
  • compared with a known-good Dataverse 5 deployment: the raw attribute contains &
  • git diff --check passes

The full HarvestingServerIT service-stack test was not run locally; the regression assertion is included for project CI.

Avoid pre-escaping the query separator before XOAI serializes the XML attribute, and cover the parsed directApiCall value in the harvesting integration test.
@pdurbin pdurbin moved this to Ready for Triage in IQSS Dataverse Project Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready for Triage

Development

Successfully merging this pull request may close these issues.

Export Failed (403) when following directApiCall URL from OAI-PMH dataverse_json record

2 participants