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

[mreekie]

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:

• Some elements in the DDI XML response have an incorrect sequence #7127 [export]
  These may need some discussion:
• Make Dataverse produce valid DDI codebook 2.5 XML #3648 [export]
• Should the Geographic Bounding Box allow optional coordinates and multiple boxes in the XML? #7108 [export]
• Add a real time validation step to the export #8702

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 IQSS/dataverse-pm#24 does that.

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

[mreekie]

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]

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]

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.