Ahasuerus - 2016-12-18
  • Description has changed:

Diff:

--- old
+++ new
@@ -1,15 +1,13 @@
 Enhance support for automated submissions. Preliminary design:

-Change the submission table to support a new submission state, “A”utomated.
-Change the Web API to accept a new flag, “Automated”. When received, the submission status will be set to “A” instead of N”.
-Create a new Web page for Automated submissions. Only editors with more than N approved submissions will be able to access it. Alternatively, we can limit access to this Web page to an explicitly defined set of editors - TBD.
-The layout of the new table will be similar to the Submission Queue table. It will have additional columns for “Held By” and “Rejection Requested”. The “Held By” column will show the user name of the user who has the submission on hold. The “Rejection Status” column will show the name of the user who submitted a request for deletion. 
-Moderators will see yet another column, which will allow them to reject submissions. It will contain the standard “Reject” link.
-When an editor clicks on a submission, the standard moderator review page will be displayed. The “Hold” button and the “Reject” area will appear as they appear to moderators. Instead of the “Approve” link, an “Edit” link will appear. (Should moderators also see the plain “Approve” link?) The “Rejection Reason” area will display the editor-submitted reason for rejection if specified (see below).
-When the reviewing editor clicks the “Hold” button, the submission will be put on hold and the editor will be returned to the list of automated submissions.
-When the reviewing editor who is NOT a moderator clicks the “Reject” button, the software will check that the “Rejection Reason” field has been populated and add the rejection reason to the submissions record (but it will not reject it). If the reviewing editor is a moderator, the software will not perform this check and will reject the submission immediately.
-When the reviewing editor clicks the “Edit” button, the submission will be automatically put on hold on the editor’s behalf. The body of the submission will be loaded into the standard “New Publication” edit form. The Moderator Note field will be pre-populated with “Original automated submission created by [robot name] and edited by [editor name].”
-When the reviewing editor clicks the “Submit” button, a new submission will be created on behalf of the reviewing editor. The original automated submission will become “Superseded”, a new state, and the “Hold” will be removed.
-There will be a page where editors will be able to view Superseded submissions.
-
-
+1. Change the submission table to support a new submission state, “A”utomated.
+2. Change the Web API to accept a new flag, “Automated”. When received, the submission status will be set to “A” instead of N”.
+3. Create a new Web page for Automated submissions. Only editors with more than N approved submissions will be able to access it. Alternatively, we can limit access to this Web page to an explicitly defined set of editors - TBD.
+4. The layout of the new table will be similar to the Submission Queue table. It will have additional columns for “Held By” and “Rejection Requested”. The “Held By” column will show the user name of the user who has the submission on hold. The “Rejection Status” column will show the name of the user who submitted a request for deletion. 
+5. Moderators will see yet another column, which will allow them to reject submissions. It will contain the standard “Reject” link.
+6. When an editor clicks on a submission, the standard moderator review page will be displayed. The “Hold” button and the “Reject” area will appear as they appear to moderators. Instead of the “Approve” link, an “Edit” link will appear. (Should moderators also see the plain “Approve” link?) The “Rejection Reason” area will display the editor-submitted reason for rejection if specified (see below).
+7. When the reviewing editor clicks the “Hold” button, the submission will be put on hold and the editor will be returned to the list of automated submissions.
+8. When the reviewing editor who is NOT a moderator clicks the “Reject” button, the software will check that the “Rejection Reason” field has been populated and add the rejection reason to the submissions record (but it will not reject it). If the reviewing editor is a moderator, the software will not perform this check and will reject the submission immediately.
+9. When the reviewing editor clicks the “Edit” button, the submission will be automatically put on hold on the editor’s behalf. The body of the submission will be loaded into the standard “New Publication” edit form. The Moderator Note field will be pre-populated with “Original automated submission created by [robot name] and edited by [editor name].”
+10. When the reviewing editor clicks the “Submit” button, a new submission will be created on behalf of the reviewing editor. The original automated submission will become “Superseded”, a new state, and the “Hold” will be removed.
+11. There will be a page where editors will be able to view Superseded submissions.