Scenario

Department Chair asks for changes from the author but does not reject the publication, so when the author attempts to resubmit the publication, the ERS will not allow it (5/06, Jorge Rey, Capinera, IN658 IN652, IN653, IN657).

Here is an sample of the email:

Procedure

1. Encourage the department chair to reject publications when changes are needed. This is how the system is designed to operate
2. Post revised pdfs in all pdf folders. Replace (do not retain) the originally submitted pdfs.
3. Notify relevant parties that the publication has been updated and can be reviewed for approval. If you have access to the EDISRouting mailbox, you can retrieve the original email sent to the approver and resend it. Cluster editors may be able to "remind" the approver from the editor section of the ERS.

Discussion

We are likely to hear of this from the person attempting to resubmit the publication. When the resubmission is made, the ERS won't route the publication, but the EDIS database is, in fact, updated. The previous version will be overwritten. I'm not sure what happens if a different version of the same DLN is submitted.

Note that in the sample above, the first author was notified of the attempted resubmission, even though it was a minor revision.

The error message should at least be changed to eliminate redundancy ("You cannot resubmit a document" or "You cannot submit a document twice"). Since in fact you can submit a document endlessly, it would be better to revise it completely to say something like, "This submission has overwritten the previous version of the document in the EDIS database, but it will not affect the routing process. The ERS will not send notice of this update to parties who have already approved the publication."