Bug 5623 - limit author upload ability to current submission step
limit author upload ability to current submission step
Status: RESOLVED WONTFIX
Product: OJS
Classification: Unclassified
Component: Authors
2.4.3
PC Mac OS X 10.6
: P5 enhancement
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-26 13:33 PDT by James MacGregor
Modified: 2013-09-03 16:40 PDT (History)
3 users (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James MacGregor 2010-07-26 13:33:38 PDT
(This bug report is somewhat related to Bug 5607. See also http://pkp.sfu.ca/support/forum/viewtopic.php?f=2&t=6386&p=24534#p24534. I believe the topic may already have come up for discussion before, and since it has some workflow implications John may want to have a say.) 

Authors should only be able to upload submissions/revisions for the submission workflow step they are currently on. For example:

-- if the submission has been submitted but not yet assigned, the author should not be able to upload a review or editing version; 

-- authors should be able to upload a revised review version (under Review -> Editor Decision) only if revisions have been requested during the review process. 

Currently, authors can only upload versions to the Editing page if specifically asked to do so; this is not the case of the Review page. My understanding is that the Review page upload feature (under Editor Decision) is left open in case the author made a mistake in the original submission upload process; but there are other ways for this to be dealt with (eg. by contacting the editor; uploading a new submission), and having the upload option to the author at all times open probably leads to more confusion than anything else.
Comment 1 John Willinsky 2010-07-28 16:15:59 PDT
Agreed.
Comment 2 Alec Smecher 2013-09-03 16:40:11 PDT
John and James, feel free to jump in if you disagree -- but given that we've had so few requests for this behavior change, I'd rather focus on OJS 3.0.