IQSS / IQSS/dataverse

Language in DDI exporter

Open
#9,266 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature: Metadata Type: Feature User Role: Guest
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Dataverse has a metadatafield "Language". But it seems there is no way to determine the language of dataset in DDI export. It seems that the only field that has language attribute is subject keyword, but it is always English, disregarding the dataset language.

What steps does it take to reproduce the issue?
Create a dataset with metadatafield "Language" selected as non-English, for example French. Publish dataset. Export DDI through UI "Metadata->DDI" or Native API.
Field stdyDscr/stdyInfo/subject/keyword" will be always with attribute "xml:lang="en" disregarding the language of the study and the controlled vocabulary will be always in English. There is no other way to determine the language of the dataset.

  • When does this issue occur?
    During DDI export.

  • To whom does it occur (all users, curators, superusers)?
    All users that use DDI export.

  • What did you expect to happen?
    ""xml:lang" attribute and controlled vocabulary to depend on language of the dataset.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by creating and publishing a dataset with a non-English Language value, then export DDI through Metadata→DDI and the Native API. Inspect stdyDscr/stdyInfo/subject/keyword, especially xml:lang and the controlled vocabulary, and trace the DDI export path. Done means both reflect the dataset language rather than always using English.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, internationalization, localization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.