Stream: troubleshooting

Topic: ampersands in metadata prevent dataset from publication


view this post on Zulip maría a. matienzo (Aug 30 2024 at 18:44):

we were having some issues with datasets publishing that have ampersands in their metadata values, e.g.

<creators><creator><creatorName>S&P Global</creatorName></creator></creators>

not an urgent thing to fix in dataverse itself (we can substitute & with and), but has there been any discussion about escaping characters/replacing them with their character entities?

view this post on Zulip Julian Gautier (Sep 03 2024 at 13:18):

Hi @María A. Matienzo. Yes there's been lots of discussion and solutions implemented to address this in a few ways.

That bit of xml you posted looks like metadata in the DataCite schema. The GitHub issue at https://github.com/IQSS/dataverse/issues/3328 was about how special characters in certain metadata fields were preventing publishing when publishing involves registering DOIs from DataCite and the pull request at https://github.com/IQSS/dataverse/pull/7798 addressed this. That fix was released with Dataverse 5.5.

Is the repository you're using using a version of Dataverse that's earlier than 5.5?

view this post on Zulip Philip Durbin 🚀 (Sep 03 2024 at 17:54):

I was gonna say... I thought we fixed that. :sweat_smile:

If it's still broken, please feel free to open a fresh issue!

view this post on Zulip maría a. matienzo (Sep 03 2024 at 17:55):

will do. @Julian Gautier this is 6.1, incidentally.

view this post on Zulip Philip Durbin 🚀 (Sep 03 2024 at 18:00):

@María A. Matienzo please feel free to try to reproduce the bug at https://demo.dataverse.org

view this post on Zulip maría a. matienzo (Sep 09 2024 at 19:30):

just getting back to this - i was unable to reproduce the bug on the demo server, but i suspect i'm running into the issue still because we're using EZID on our end (see https://github.com/IQSS/dataverse/issues/3328#issuecomment-819837590)

view this post on Zulip maría a. matienzo (Sep 09 2024 at 19:34):

looks like this issue has been closed - i understand that it's low priority, but what would be the best way to get an issue on the backlog for this (i.e. opening a new one vs. something else)?

view this post on Zulip Philip Durbin 🚀 (Sep 09 2024 at 20:02):

A fresh issue would be ideal.

view this post on Zulip maría a. matienzo (Sep 09 2024 at 22:06):

https://github.com/IQSS/dataverse/issues/10830

view this post on Zulip Philip Durbin 🚀 (Sep 09 2024 at 22:42):

Thanks! It looks like DOIEZIdServiceBean was removed in https://github.com/IQSS/dataverse/commit/44ce6a19c72c7c4c3c156e44fa56de5d89613106 in Dataverse 6.2. Is there any chance you could re-test with 6.2 or 6.3 (or the "develop" branch, if you're brave)?

view this post on Zulip maría a. matienzo (Sep 09 2024 at 22:43):

we're getting ready to deploy 6.3 to prod this week - i'll test it then.

view this post on Zulip Philip Durbin 🚀 (Sep 09 2024 at 22:43):

Awesome. Thanks!


Last updated: Oct 30 2025 at 06:21 UTC