thejmfc (Jul 27 2023 at 10:05): thejmfc (Jul 27 2023 at 10:05):Hi @Philip Durbin . I've got another question related to the metadata blocks.
I've found out that the Citation Metadata Block does not fully comply with the CESSDA DDI 2.5.
It requires a certain 'date' field that is not being provided.
image.png
image.png
I've managed to 'trick' the CESSDA validator by feeding it a DDI xml with the <date> instead of <distDate>, but this is a suboptimal solution.
Is this an issue you were aware of? Should I create an issue :D?
Philip Durbin 🚀 (Jul 27 2023 at 13:24):I asked the developer who fixed up DDI in 5.14 (not out yet) to take a look.
Leo Andreev (Jul 31 2023 at 22:41):Hello,
We recently merged the PR https://github.com/IQSS/dataverse/pull/9484 and it will become part of Dataverse 5.14, which is being released very shortly. The specific goal of that PR was to make Dataverse produce DDI xml that passes the validation by https://cmv.cessda.eu/#!validation. So I would suggest to upgrade to 5.14 and try again.
I'm cautiously optimistic that it will resolve your problem. But it is not completely impossible for your datasets to contain some combination of metadata that we somehow missed while testing, that will still result in invalid DDI... so that's the reason I'm not saying that it's "guaranteed" to fix it for you.
If you run into any problems, please open a new issue and we'll try to fix it asap. We are interested in keeping it valid going forward.
best,
-L.A.
P.S. It's not shown in your screenshot, but what validation profile are you using? We've been testing under "CESSDA DATA CATALOGUE (CDC) DDI2.5 PROFILE - MONOLINGUAL: 1.0.4".
thejmfc (Aug 01 2023 at 10:45):Leo Andreev disse:
Hello,
We recently merged the PR https://github.com/IQSS/dataverse/pull/9484 and it will become part of Dataverse 5.14, which is being released very shortly. The specific goal of that PR was to make Dataverse produce DDI xml that passes the validation by https://cmv.cessda.eu/#!validation. So I would suggest to upgrade to 5.14 and try again.
I'm cautiously optimistic that it will resolve your problem. But it is not completely impossible for your datasets to contain some combination of metadata that we somehow missed while testing, that will still result in invalid DDI... so that's the reason I'm not saying that it's "guaranteed" to fix it for you.
If you run into any problems, please open a new issue and we'll try to fix it asap. We are interested in keeping it valid going forward.
best,
-L.A.
P.S. It's not shown in your screenshot, but what validation profile are you using? We've been testing under "CESSDA DATA CATALOGUE (CDC) DDI2.5 PROFILE - MONOLINGUAL: 1.0.4".
It might be the Dataverse version, as we're using 5.13. I'll see about an update :) Thanks for the information.
Leo Andreev (Aug 02 2023 at 23:14):It might be the Dataverse version, as we're using 5.13
It is definitely broken - as in, generates invalid DDI - in 5.13. But 5.14 should now be out in a couple of days.
Philip Durbin 🚀 (Aug 14 2023 at 13:30):@thejmfc Dataverse 5.14 is out. Please give it a try.
thejmfc (Aug 17 2023 at 10:59):Philip Durbin disse:
thejmfc Dataverse 5.14 is out. Please give it a try.
Hi Phil. I think the issue was sorted after we installed 5.14.
I've changed jobs and are no longer associated with this Dataverse installation.
I'll still be around though. :)
Philip Durbin 🚀 (Aug 17 2023 at 11:17):Oh! Congrats on the new job! Glad to hear you'll still be around. :big_smile:
Notification Bot (Sep 07 2023 at 10:44):Philip Durbin has marked this topic as resolved.
Last updated: Oct 30 2025 at 06:21 UTC