[CoLab] Allow author 'submit a new version'
Description; currently, the editor is required to manually set the Decision verdict
to 'Revise' in order to display the 'Create new version' button for authors. This makes sense for a traditional journal publishing workflow, but less so for a PRC workflow. For a PRC workflow, the author is required to action the following steps;
- receive peer review feedback on preprint version 'X' (v1) in kotahi
- provide a response to version 'X' (v1) peer review feedback in kotahi
- submit a new preprint version (v2) to a preprint server
- submit the new version URL for peer review in kotahi
- back to 'step 1'
The purpose of this task is to provide a configuration option that presents the option to 'create new version' at the optimum time in the workflow, mitigating the need for the editor to set the Decision to 'Revise'.
Acceptance criteria;
-
The 'Submit a new version' button should display at all times on the /submit
page. Title; 'Submit a new version'. Paragraph text; 'You may modify and resubmit a new version of your manuscript'. Button text; 'Submit a new version'. -
ThreadedDiscussion
data captured in the submission form should persist across versions. Only the latest version should remain editable. Previous versions should be read-only.ThreadedDiscussion
data should also persist in the Decision form. -
Configuration variable to display the create new version button on the submit page; DISPLAY_CREATE _NEW_SUBMISSION=
true/false. Add variable to Configuration>Submission>Create new submission.