You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In continuation to issue #298, which probably requires a lot of work and thus might be unrealistic, it seems like the following may be an easier way to provide some minimal support for the concept of revise-resubmit between consecutive review cycles:
Allow an administrator to set the minimal paper number allocated to submissions.
Allow an administrator to change the number of a new submission to another number.
This way, the minimal paper number of Cycle 2 can be set to be greater than all the submission numbers of Cycle 1. Then, when a revise-resubmit paper is submitted to Cycle 2, the admin can change its number to be its previous number from Cycle 1.
(The credit for this idea belongs to Mike Swift.)
The text was updated successfully, but these errors were encountered:
If the submission ID is made unique across cycles (for all submissions, not just revise-resubmit), it would make searching for a specific submission easier, allowing us to use the same query across HotCRP instances as well as in our email.
In continuation to issue #298, which probably requires a lot of work and thus might be unrealistic, it seems like the following may be an easier way to provide some minimal support for the concept of revise-resubmit between consecutive review cycles:
Allow an administrator to set the minimal paper number allocated to submissions.
Allow an administrator to change the number of a new submission to another number.
This way, the minimal paper number of Cycle 2 can be set to be greater than all the submission numbers of Cycle 1. Then, when a revise-resubmit paper is submitted to Cycle 2, the admin can change its number to be its previous number from Cycle 1.
(The credit for this idea belongs to Mike Swift.)
The text was updated successfully, but these errors were encountered: