Feature Request: Provide a third "Approved - Ready to Publish" option as response to "Submit for Review"
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 Feature Request
Provide a third option "Approved - Ready to Publish" (or similar) as response to a dataset that has been Submitted for Review as the dataset might be deemed in good order for publishing but the reviewer doesn't want to actually publish it yet.
What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)
Depositor -> not sure what the reviewer role is
What inspired the request?
ADA implements a self-deposit dataverse where depositors are set up to create their datasets with metadata, files, etc. When they are ready to submit it to the archivist team for processing, they click 'Submit for Review'.
Currently there are only 2 options that the reviewer can select: Publish or Return to Author.
ADA does not publish datasets on its deposit dataverse. So the datasets that can be 'Approved' sit in 'InReview' status forever.
Additionally, ADA would like to have the status of a dataset set to "Approved" be the "Ingest" event in the OAIS model that ADA follows. Currently, as datasets ready to publish aren't 'Returned to Author', and they are never published on our deposit dataverse, there is no trigger event that can be labelled as the "Ingest" event.
What existing behavior do you want changed?
Provide more than 2 options for "Submitted for Review" response.
Any brand new behavior do you want to add to Dataverse?
Add the "Approved - Ready to Publish" or "Approved" or "Ready to Publish" (it can likely be changed in the Bundle.properties file) 3rd option.
Any open or closed issues related to this feature request?
Not sure.
Are you thinking about creating a pull request for this feature?
No resources to do so.
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 Submit for Review response flow and the existing Publish and Return to Author options, then inspect Bundle.properties for the response labels. Determine where review status transitions are handled and how the new Approved or Ready to Publish state should behave. Done means the third option is available with the intended label and status without publishing the dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100