IQSS / IQSS/dataverse-frontend
Edit Dataset Terms Should Return to latest Draft Dataset
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
What steps does it take to reproduce the issue?
-
When does this issue occur?
edit terms save changes -
Which page(s) does it occur on?
dataset -
What happens?
Currently, after saving the change, the page jump to latest published dataset, but what we expect is jumping to a draft dataset so the user could publish again to apply the changes of terms -
To whom does it occur (all users, curators, superusers)?
-
What did you expect to happen?
Which version of Dataverse Frontend are you using?
v. 6.10.1
frontend version: 903a8c69d
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:
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
Reproduce the issue on the dataset page by editing terms and saving changes, then trace the frontend's post-save navigation. Done means the save flow returns to the latest draft dataset rather than the latest published dataset, so the user can publish the updated terms.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100