Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Language controlled vocabulary displays 'Logudorese Sardinian, Croatian' instead of 'Croatian'

Open Beginner friendly
  • Is something wrong?
#12,818 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
internationalization

Research direction

Read the affected entries in scripts/api/data/metadatablocks/citation.tsv and src/main/java/propertyFiles/citation.properties. Separate the Croatian and Logudorese Sardinian vocabulary records, then check that each language has the correct displayed label in the alphabetical sections. Done when Croatian appears as its own entry under C and Logudorese Sardinian appears under L in the dataset language dropdown.

Written by the indexing model from the issue text.

Description

What steps does it take to reproduce the issue?

  • When does this issue occur?
    When selecting the language of a dataset in the Citation metadata block.

  • Which page(s) does it occur on?
    Dataset create / edit metadata page (dataset.xhtml).

  • What happens?
    In the Citation Metadata controlled vocabulary dropdown for the Language field (language), Croatian is displayed as Logudorese Sardinian, Croatian instead of Croatian. When typing "Croatian" into the dropdown filter, it only matches this combined entry.

  • To whom does it occur (all users, curators, superusers)?
    All users editing dataset citation metadata.

  • What did you expect to happen?
    The dropdown should display Croatian as its own entry under "C".

Which version of Dataverse are you using?
Affects all versions from v6.4 up to and including v6.12.1 and current develop branch.

Root Cause Analysis:

Two lines were concatenated during the expansion of the ISO 639 language controlled vocabulary in v6.4:

  1. scripts/api/data/metadatablocks/citation.tsv (line 1561 on develop):

    	language	Croatian	hrv	1418	hrv	Logudorese Sardinian	src	hr	Croatian

    The record for Croatian (hrv, ISO 639-1 hr) and Logudorese Sardinian (src) were accidentally joined into a single TSV line without a newline delimiter.

  2. src/main/java/propertyFiles/citation.properties (line 4093 on develop):

    controlledvocabulary.language.logorik=Logorik
controlledvocabulary.language.croatian=Logudorese Sardinian, Croatian
controlledvocabulary.language.lohorung=Lohorung
    • controlledvocabulary.language.croatian is incorrectly placed in the "L" alphabetical section between logorik and lohorung (where Logudorese Sardinian belongs).
    • controlledvocabulary.language.croatian is completely missing from the "C" section (after croatia_sign_language).

Suggested Fix:

  1. In scripts/api/data/metadatablocks/citation.tsv:
    Restore the discrete Croatian entry and separate Logudorese Sardinian:

    -	language	Croatian	hrv	1418	hrv	Logudorese Sardinian	src	hr	Croatian
+	language	Croatian	hrv	1418	hrv	hr
+	language	Logudorese Sardinian	src	3785	src

  2. In src/main/java/propertyFiles/citation.properties:
    Add controlledvocabulary.language.croatian=Croatian to the "C" section:

    controlledvocabulary.language.croatia_sign_language=Croatia Sign Language
controlledvocabulary.language.croatian=Croatian
controlledvocabulary.language.cross_river_mbembe=Cross River Mbembe

    And update line 4093 in the "L" section:

    controlledvocabulary.language.logorik=Logorik
controlledvocabulary.language.logudorese_sardinian=Logudorese Sardinian
controlledvocabulary.language.lohorung=Lohorung

Any related open or closed issues to this bug report?
None found.

Are you thinking about creating a pull request for this issue?
Yes, we have verified this patch on Payara 7 / JDK 21 / Dataverse 6.12.1 and can provide a PR against develop if requested.

Dominant language
Java
Stars
1.1k
Forks
568
Avg merge
5d 7h
Merged PRs (30d)
26

Getting set up

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.

More from IQSS/dataverse

All issues in IQSS/dataverse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.