Dataverse should use ISO codes for languages when exporting and importing metadata.

[JingMa87]

"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.

[pdurbin]

Related:

• As a researcher, I need more language options to better describe my data #4589
• Missing 639-3 language codes? #7757

[pdurbin]

@JingMa87 is no longer working on the issues he opened: #7412 (comment)

We should check with the DANS crew to see if any of them are still interested in this: @PaulBoon @janvanmansum @WittenbergM @LauraHuisintveld

[janvanmansum]

@pdurbin : no longer a priority for DANS.