Harvesting: DDI import fails when there's a `xml:lang` attribute present in the `codeBook` element
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
There appears to be an import bug, where a ddi with the xml attribute xml:lang in the codeBook element cannot be imported. It does not appear to be a result of the actual value of the attribute being invalid. In the DDIs that triggered the issue in prod. all of these were xml:lang=en and "en" is a perfectly valid CVV.
The issue can be described as minor, on a large scale of things (in terms of the number of datasets affected - all of them in Recherche Gouv - vs the total number of harvested datasets). However, it makes most of the datasets in that specific collection unimportable.
Will attach an example of a DDI. (todo)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Dataverse harvesting import with a DDI whose codeBook element includes xml:lang="en"; the issue does not name a source file or test. Done means the DDI imports successfully when that attribute is present, without depending on the attribute value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100