PKP Bugzilla – Bug 4481
Abstract followed by presentation workflow issues
Last modified: 2009-07-06 19:18:24 PDT
We are moving to Git Issues for bug tracking in future releases. During transition, content will be in both tools. If you'd like to file a new bug, please create an issue.
MODE: Abstract review, followed by presentation review
1. Author submits abstract
2. Director is able to select reviewer and receive review
3. (a) Director rejects -> end of line
3 (b) Or director requests changes [I would think no re-review possible except by director, but it may not be set this way]
3. (c) Or director accepts and “invites presentation” (status)
4. If accepted, only then can author submit presentation and does so (Abstract needs to be still revise-able by author to match the actual paper submitted, much like other metadata).
5. Once presentation is submitted, director is able to select reviewer and receive review
6 (a) Director rejects presentation -> end of line
6 (b) Director requests changes -> able to notify or replace previous reviewer of presentation, or make decision herself.
6 (c) Director accepts paper
Thanks for the clarification, John. I think the current implementation
makes all of this possible, however, after 6b the submission status is
reset back to the abstract review stage, which seemed confusing to me
(in terms of what the author and director will expect and see).
Yes, the reset to abstract stage does not seem right, and it should stay in the presentation review stage, which should remain open until the director says yeah or nay.
Related to this, it seems that the revisions required
decision for the presentation should also be displayed against the
paper review. Currently, it's being made in the paper review stage but
displayed as part of the abstract review decision (appended to the
previous invite presentation decision).
Should this be marked against 2.3, i.e. will there be a 2.1.3 release? I'm
currently working on OCS 2.3 submission issues (there are many), I can factor
Yes, reassigning to OCS 2.3 -- please assign all future bugs likewise. The OJS 2.2.x and OCS 2.2.x stable lines are closed except for critical security fixes.
Yes, sounds good Matt.
Ok, assigning to myself. NB I am also fixing other issues with submissions (mostly submissions without supplementary files and some other problems resulting from the switching of steps 2 and 3).
Created attachment 2072 [details]
Patch against OCS pre-2.3 CVS
Fixed. (This will require thorough testing -- I gave my all and it seems to work fine, but its pretty crazy code and I'm still not 100% sure its following specified workflow procedures).
Did some initial testing and looks good, Matt.