PKP Bugzilla – Bug 2319
Author's Review page
Last modified: 2013-05-29 15:00:47 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.
Decision Accept Submission 2006-06-24
AS AUTHOR SHOULD NOT HAVE ACCESS TO THIS, BUT ONLY THE CORRESPONDENCE FROM EDITOR
THE DATE SHOULD REFLECT THE FIRST REVIEW "UNDERWAY"
NOT SURE WHAT THIS IS ANY MORE, AS Review Version WILL HAVE LATEST DATE, SO MAY NOT BE
IS THIS THE Supplementary File? AGAIN, MAY NOT BE NEEDED (as Supp Files are on Summary page)
ADD UNDER Review initiated...
Peer Reviewers 3
THIS SHOULD BE None UNTIL THE EDITOR ACTUALLY UPLOADS A FILE IN EDITOR DECISION, RATHER
THAN PREVIOUS VERSION WHICH HAD REVIEW VERSION BECOME EDITOR VERSION
Author Version None
Upload Author [Browse] [ ] [Upload]
Author Version None
Upload [Browse] [ ] [Upload]
Sent to Copyediting
WHICH WILL APPEAR ON THE SAME LINE AS THE VERSION THAT THE EDITOR HAS SENT TO
The help file <topic id="editorial/topic/000026" locale="en_US" title="Editor Decision" toc="editorial/toc/000006" key="editorial.sectionEditorsRole.review.editorDecision">
States exactly what this bug report says. The author doesn't have access to the editor's decision.
However, current version still shows the editorial decision on the author's page, just like OJS1 and as I believe it should. There is no reason why the author shouldn't be able to see the editorial decision.
The bug I see happening is that the comments made to the author by the reviewer are not being displayed anywhere. Is the Editor supposed to copy and paste the comments made to the author, just like OJS1? If that's the case, then I would suggest the following:
1- Editor can edit reviewer comments made to author, somehow creating a new "correspondance" to the author (identifying by letter which reviewer made what comment), and creating a checkbox that will enable access to these comments or not. I believe, if this is possible, that this would speed up editorial tasks immensely.
Deferring from 2.2.
Zombie entry; superseded by 3.0 UI work.