-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Broken OAI records for some datasets with UTF-8 characters #9910
Comments
2023/09/13: Added to the Global Backlog, with a very strong proposal for inclusion in release 6.1. |
2023/09/18
|
2023/09/25: Applied the NIH GREI 2.4.1B tag to reflect value to harvesting. |
Much of the discussion related to this bug happened on slack between @poikilotherm, @jggautier, @scolapasta and I, so just to add a quick summary here:
|
Just to make sure this doesn't get lost: there is an upstream lib PR waiting for review gdcc/xoai#192 |
Thank you @poikilotherm, much appreciated! I was a little busy putting out some fires, but looking at the xoai pr now. |
XOAI 5.2.0 is on it's way to Central, might take a moment until it's retrievable. |
OK, we'll move this along and update the Dataverse pom file. And then we'll just need to test/QA the result. |
Quick question: I've been assuming that the xoai jars v. 5.1+ are no longer compatible with pre-6.0 versions of Dataverse, is that actually correct?
|
Should be compatible. |
I'm going to make a quick PR incorporating xoai-5.2 into develop. |
@DS-INRA (and everybody who may be interested) The linked PR #10012 has been merged, so the bug is now fixed for real in the develop branch. To clarify, I have tested patching these jars in place, on an instance where the standard 5.14 release was deployed. I haven't tried building dataverse-5.14.war from sources with these libraries, but can't think of a reason why that wouldn't work either. If there is interest, I can produce a patched dataverse-5.14.war as well. The library jars in question can be found on maven central - at |
(Edit: everything entered in this issue so far was a red herring; I'm deleting everything and rewriting the issue from scratch)
The issue was opened as a followup to an RT ticket from an outside institutions. They were unable to harvest the full OAI set from IQSS, because it was reliably bombing on the same invalid record.
The problem was traced to something inside the OAI library, it is being tracked in gdcc/xoai#188 in the xoai repo. I have a rough idea of how to produce a quick fix.
The text was updated successfully, but these errors were encountered: