jggautier
commented
7 years ago Thanks @jomtov for moving this issue from our support system!
I thought it might be helpful to give some background on the issue, list what might need to change when the DDI xml is made valid, and describe the errors.
As background for anyone else interested, the DDI xml that Dataverse generates for each dataset (and datafile) needs to follow DDI's schema, so that other repositories and applications using DDI xml can use it (e.g. during harvesting).
To answer jomtov's question, I think Dataverse's xml would need to be corrected. After fixing the errors and making sure the XML is valid, these are what I imagine will need to be adjusted:
- the scripts used to pull Dataverse metadata into the DDI xml
- possibly other applications that use parts of the DDI xml that Dataverse produces. (Scholars Portal's Data Explorer uses parts of the DDI (variable level metadata) that is valid)
There are five errors here, described in the dataverse_1062_philipsonErrorTypes.txt file in jomtov's post:
1. DDI schema doesn't like "DVN" as a value for source in <verStmt source="DVN">
Only "archive" and "producer" are allowed as values.
2. DDI schema doesn't like the URI attribute being called "URI":
_Attribute 'URI' is not allowed to appear in element 'keyword'._
As jomtov points out, the keyword URI is called vocabURI in Dataverse. Unless there's a reason why it's called URI in the DDI XML, I think this is as easy as changing "URI" to "vocabURI", which is okay with the schema.
<keyword vocab="term" vocabURI="http://vocabulary.org/">Metadata</keyword>
3. DDI schema doesn't like where "contact" info is placed:
<sumDscr/>
<contact affiliation="A University" email="email@domain.com">Name</contact>_Invalid content was found starting with element '{"ddi:codebook:2_5":contact}'. One of '{"ddi:codebook:2_5":sumDscr, "ddi:codebook:2_5":qualityStatement, "ddi:codebook:2_5":notes, "ddi:codebook:2_5":exPostEvaluation}' is expected._
The DDI schema says that sumDscr shouldn't hold things like contact info. The contact element should be under useStmt:
<useStmt>
...
<contact affiliation="A University" email="email@domain.com">Name</contact>
...
</useStmt>4 and 5. DDI schema doesn't like <useStmt> being followed by a value, here the value being the license:
<useStmt>CC0 Waiver</useStmt>
Two of the elements that can be nested under <useStmt> are <restrctn> and <conditions>. Either element seems appropriate for holding license info. to me. The schema's descriptions of the two elements makes <conditions> sound like a catchall and <restrctn> sound like the primary element to use. However, ICPSR uses <conditions> for license-like info.
Lastly, this isn't one of the five errors reported, but DDI likes <dataAccs> a level under <useStmt>. (Right now it's a level under <stdydscr>.) So the following change should fix these errors:
<useStmt>
<dataAccs>
<conditions>CC0 Waiver</conditions>
<contact>...</contact>
</dataAccs>
</useStmt>
pdurbin
jomtov
mheppler
JingMa87
poikilotherm
BPeuch
qqmyers
mreekie
Forwarded from the ticket: https://help.hmdc.harvard.edu/Ticket/Display.html?id=245607
Hello, I tried to validate two items exported to DDI from dataverse.harvard.edu with codebook.xsd (2.5) and got the same types of validation errors described below for item1 (below the line, should work as a well-formed xml-file):
Item 1:https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/BAMCSI
Item 2: https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/P4JTOD
What could be done about it (else than meddling with the schema?)
Best regards,
Joakim Philipson Research Data Analyst, Ph.D., MLIS Stockholm University Library
Stockholm University SE-106 91 Stockholm Sweden
Tel: +46-8-16 29 50 Mobile: +46-72-1464702 E-mail: joakim.philipson@sub.su.se http://orcid.org/0000-0001-5699-994X
<?xml version="1.0" encoding="UTF-8"?>
dataverse_1062_philipsonErrorTypes.txt