IQSS / IQSS/dataverse

Reason not shown when changing retention/embargo of draft file

Open
#12,432 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Type: Bug
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

What steps does it take to reproduce the issue?

  1. Add a file to an existing or new dataset.
  2. Save the changes
  3. Select retention period or embargo from edit files, fill in a reason and save the changes
  4. Repeat step 3: the reason is not shown
  • When does this issue occur?

While working on a draft dataset.

  • Which page(s) does it occurs on?

https://demo.dataverse.org/dataset.xhtml

  • What happens?

No content in the reason field in step 4

  • To whom does it occur (all users, curators, superusers)?

Curators and dataset owners.

  • What did you expect to happen?

Content in the reason field.

Which version of Dataverse are you using?

v. 6.10.1 build iqss-2

Any related open or closed issues to this bug report?

Screenshots:

No matter the issue, screenshots are always welcome.

To add a screenshot, please use one of the following formats and/or methods described here:

Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?

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 on the dataset.xhtml page using the listed steps: add a file, save the draft, set a retention period or embargo with a reason, then reopen the edit form. Trace the draft dataset file-editing flow and verify that the entered reason is shown when the retention or embargo is edited again. Done means the reason field retains and displays its saved content for curators and dataset owners.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.