Suggestion:limit or filter languages pack (set favourite)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Overview of the Suggestion
In Dataverse support fo all ISO 639-3 languages was introduced. However in many cases limitation or setting preferred languages would be nice, mainly from ux point of view.
What kind of user is the suggestion intended for?
Mainly depositor and Guests (usage of search).
What existing behavior do you want changed?
I would like to be able to indicate the list of selected languages mainly used in a given repository. These languages would appear at the top of the language selection list when creating a dataset and when using search.
This idea was mentioned on group forum: https://groups.google.com/u/1/g/dataverse-community/c/3T1XW4oWcvQ/m/O3zz3PNGAwAJ
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
Start by tracing the language-selection controls used during dataset creation and in search, then identify where repository-level language preferences could be configured. Done means selected languages are consistently prioritized in both contexts without removing access to the full ISO 639-3 list; the issue names no files or tests, so confirm the relevant entry points and add coverage for both workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- internationalization, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100