IQSS / IQSS/dataverse-frontend
Feature Request/Idea: Return to Author
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
Curators often return datasets to the author because the dataset is not ready to be published. They can leave a note for the author, as shown in the screenshots below.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Curator
What inspired the request?
Conversations with @sbarbosadataverse and @dliburd about how they could probably do much more of their job without ever leaving the SPA if they had this "Return to Author" button. Obviously, we've been prioritizing features for depositors but this one feature, which I hope is somewhat small to implement, could leave to Sonia and Dwayne spending much more time in the SPA in production, providing valuable feedback on a whole variety of features.
Design considerations
We got feedback in #243 "that the popup is not really adapted for long texts" but the screenshot there (also included below) shows a much lower character count so maybe it's ok, as-is:
API endpoints
The following API endpoint should be used: Return a Dataset to Author
Any open or closed issues related to this feature request?
I will close the following related issues in favor of the new one I'm creating now:
- #201
- #243
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 with the Dataverse native API endpoint “Return a Dataset to Author” and review related issues #201 and #243. Then locate the curator workflow in the SPA and its existing dialogs or dataset actions. Done means curators can return an unpublished dataset to its author with a note without leaving the SPA.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100