Improve DDI harvesting by making it compatible with metadata customizations in TSV files made by Dataverse administrators.
What kind of user is the feature intended for?
superuser, system administrator, configuring harvesting clients
What inspired the request?
We have metadata customizations in our TSV files.
For example, unitOfAnalysis is not by default a ControlledVocabulary type while it is the case on our installation
As a result, DDI harvesting does not work and generates an error of type:
class edu.harvard.iq.dataverse.util.json.JsonParseException (incorrect typeClass for field unitOfAnalysis, should be controlledVocabulary)
Currently, during a DDI harvest, the data type mapping is hardcoded, without directly relying on the corresponding TSV file.
The goal of the issue is that the harvester bases itself on the TSV directly to adapt to customizations.
Overview of the Feature Request
Improve DDI harvesting by making it compatible with metadata customizations in TSV files made by Dataverse administrators.
What kind of user is the feature intended for?
superuser, system administrator, configuring harvesting clients
What inspired the request?
We have metadata customizations in our TSV files. For example,
unitOfAnalysisis not by default aControlledVocabularytype while it is the case on our installation As a result, DDI harvesting does not work and generates an error of type:This is because the data type is hardcoded :
https://github.com/IQSS/dataverse/blob/3305c4a41045d0bb2f261c5eb2aa93414a34f2c6/src/main/java/edu/harvard/iq/dataverse/api/imports/ImportDDIServiceBean.java#L794-L796
What existing behavior do you want changed?
Currently, during a DDI harvest, the data type mapping is hardcoded, without directly relying on the corresponding TSV file. The goal of the issue is that the harvester bases itself on the TSV directly to adapt to customizations.