search

IQSS / dataverse

Open source research data repository software
http://dataverse.org
Other
878 stars 490 forks source link

PM.Epic: Make sure our DDI is valid against the schema - deprecated #8701

Closed mreekie closed 1 year ago

mreekie commented 2 years ago

From Leonid The following issues are about the DDI exporter producing XML that is not valid under the schema. I would consider creating a wider scope umbrella issue, something like "Make sure our DDI is valid against the schema (and maybe add a real time validation step to the export?)

The first one is ready to be worked on, I believe:

The first step in the Harvesting NIH deliverable was figuring out what has already been done by the dataverse team and by the community towards this aim and what still remains to be done. Leonid's conclusions at https://github.com/IQSS/dataverse-pm/issues/24 does that.

This issue was orginally raised as part of https://github.com/IQSS/dataverse-pm/issues/25# . It was broken out as suggested as a seperate epic.

mreekie commented 1 year ago

Closing Since we've talked further we have determined that This does not add any context to the CDI-DDI deliverable anymore. (CDI-DDI are two different animals)

mreekie commented 1 year ago

Tentatively adding the issues in this epic to NIH OTA 1.4.1 and re-opening the issues. This may be a mistake since I remember from the discussion of 1.2.2 versus 1.4.1 there was some disagreement as to where these issues belonged..

mreekie commented 1 year ago

Closing issue again. Talked with Leonid today. He is going through the issues in IQSS/dataverse-pm#24 This is where this issue was originally derived. Having this issue is redundant since we're taking a fresh look at that whole list.