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.

Bug 8314 - Implement ability to promote from review into production
Implement ability to promote from review into production
Status: NEW
Product: OJS
Classification: Unclassified
Component: General
All All
: P3 normal
Assigned To: PKP Support
Depends on:
Blocks: 8332
  Show dependency treegraph
Reported: 2013-07-16 16:03 PDT by Alec Smecher
Modified: 2013-08-15 14:43 PDT (History)
1 user (show)

See Also:
Version Reported In:
Also Affects:


Note You need to log in before you can comment on or make changes to this bug.
Description Alec Smecher 2013-07-16 16:03:12 PDT
Currently the file selector in the "send to production" allows for the selection of files to be made available to the Author, not files to be included in production; to bring in existing files, it's necessary to click the upload/select action in the production grid and select files there, which feels like backtracking.

Consider popping up a second modal after the author is notified that allows files to be selected? Perhaps a wizard to guide through both steps?
Comment 1 Alec Smecher 2013-07-22 13:45:55 PDT
(Alec will ask John about the potential for using the same file selection for both purposes, i.e. choosing what's shown to the author and promoting those to production.)
Comment 2 John Willinsky 2013-07-24 22:47:55 PDT
Clicking on "Accept Submission" calls up a modal that includes a Notify Author email and a Send Files to Editing table, listing the submission file. 

We have been talking about having the files checked off as selected by default, but it strikes me that the more direct way of doing this is to work with the assumption that they are all going forward and use the checkboxes only for "Do not send" which would be the title for the column of checkboxes. I realize that we may be using already checked-to-include by default elsewhere but I ask that we consider using this check-to-exclude approach as more direct.
Comment 3 Alec Smecher 2013-07-25 10:15:58 PDT
John, I assume authors also be allowed to see the files that were checked, in addition to those files moving into Production?

I'd find "check to exclude" very counter-intuitive.
Comment 4 John Willinsky 2013-07-26 17:12:54 PDT
Authors should have access through their access to the Review and Editing stages to the files. On reflection, I do not think that they need to be notified of which files are forwarded.

If we present to editors a table in the Accept Submission modal (which includes Notify Author) that includes all submission files and is entitled...

Select Files to Send to Editing
[ ] File1
[ ] File2
[ ] File3

And it would not close if no files are selected, would it be more intuitive?