Dataverse should use ISO codes for languages when exporting and importing metadata.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
"I think we agree that it would be preferable if Dataverse shows the depositor the full language, e.g. "English", but uses the corresponding ISO codes in the metadata exports, e.g. <dc:language>en</dc:language> for the OAI-PMH feed and <dcterms:language>en</dcterms:language> for the DC Terms metadata available through the metadata export dropdown and the API.
Then the other way around, on import, Dataverse will need to know that <dc:language>en</dc:language> means that the Language value it should display on the dataset page UI is "English" (for repositories in English)
Does internalization need to be considered? E.g. when dataset metadata is imported into an installation with "Spanish" internalization, <dcterms:language>en</dcterms:language> should be displayed on the dataset page as the localized value "Inglés"?"
@jggautier
Version: 4.20.
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
Trace language handling through the OAI-PMH feed, DC Terms metadata export dropdown, API, and dataset import/display flow. Check how ISO codes map to localized names, including the Spanish UI case, and identify the relevant tests. Done means exports use ISO codes and imports display the corresponding localized language.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100