IQSS / IQSS/dataverse-frontend

Add tooltips to status labels

Open
#426 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
31
Forks
26
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Overview of the Feature Request

Add tooltips on labels for dataverse collections, datasets and files statuses.

What kind of user is the feature intended for?

Any user, but mostly for depositors

What inspired the request?

Beginners at depositing sometimes don't understand well the notions "Unpublished", "Draft", "In Review" and their differences.
It is even more true with other labels like curation labels (separate issue)

Any brand-new behavior do you want to add to Dataverse?

Add tooltips to the status labels :

https://github.com/IQSS/dataverse-frontend/assets/46443753/1ca745ba-9472-4ce8-98eb-41e9bb07a8ad

Allow these tooltips to be internationalized.

Any open or closed issues related to this feature request?

None seen

Tooltips text suggestion

Dataverse collection

  • Unpublished : This collection is not published, publish it so that others can see it. Once public, it can no longer be unpublished.

Dataset

  • Unpublished : This dataset has never been published, publish it so that others can see it.
  • Draft : This version of the dataset is in draft state, publish it so that others can see these changes.
  • Version x.y (ideally > 1.0) : Previous versions can be accessed in the "Version" tab of this dataset.

File

  • Unpublished : This file has never been published, it will be published when you publish the hosting dataset.
  • Draft : This version of the file is in draft state, it will be published when you publish the hosting dataset.
  • Version x.y (ideally > 1.0) : Previous versions can be accessed in the "Version" tab of this file.

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

No source file, test, or entry point is named in the issue. Start by locating the collection, dataset, and file status-label components and existing tooltip and internationalization patterns; the work is done when the specified status labels show the proposed localized explanations.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, internationalization
Issue type
Feature
Difficulty
3/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.