IQSS / IQSS/dataverse

Add duplicate title, subject, and description fields for text in multiple languages

Open
#4,633 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Having fields like title and description offer alternative language versions would also be helpful for discovery.

From Julian: from what I can tell so far, DataCite 3.1 schema lets you specify the language of Title, Subject and Description with a long attribute (4.1 adds the xml lang attribute to Rights) - https://schema.datacite.org/meta/kernel-4.1/doc/DataCite-MetadataKernel_v4.1.pdf. The schema says it accepts only IETF BCP 47 and ISO 639-1 language codes. But I don't think Dataverse knows the ISO language codes for the languages it displays in the Citation block (I vaguely remember a comment about this in a github issue or maybe a Google Group post but can't find it). The Consorcio Madroño Dataverse does this with the DataCite metadata they publish for each dataset: https://edatos.consorciomadrono.es/api/datasets/export?exporter=oai_datacite&persistentId=doi%3A10.21950/O53TLR

And most or all of the DDI elements that Dataverse uses can include a lang attribute (http://www.ddialliance.org/Specification/DDI-Codebook/2.5/XMLSchema/field_level_documentation_files/schemas/xml_xsd/attributes/lang.html). Looks like it accepts any value for now.

see related ticket https://github.com/IQSS/dataverse/issues/4632 for adding record language qualifier

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

Start by reviewing related issue #4632 and the linked DataCite 4.1 and DDI language specifications. Trace the metadata export endpoint and determine how Title, Subject, and Description are represented today. Done should include an agreed design for language-qualified alternatives and its DataCite/DDI export behavior.

Written by the indexing model from the issue text.

Assessment

Domain
internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.