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
Joppe has suggested that we try to make the default paper order for an issue align to the order in which they were submitted to hotcrp. The way it works now is that when a paper is uploaded to publish.iacr.org, the paper number is assigned then to be the next one in order. This is much like the paperid that is assigned when something is submitted to hotcrp. Unfortunately if we assign paperno differently, it has the potential to cause havoc with different people looking at the list of papers, because a reassignment of paperno will invalidate the view that someone has in their browser.
I think the only solution is to add a button that would be used after all papers have been uploaded to publish.iacr.org to reorder the paperno by the value of the paperid (in reality we would use the submitted value, since that is easier to sort on).
The text was updated successfully, but these errors were encountered:
Joppe has suggested that we try to make the default paper order for an issue align to the order in which they were submitted to hotcrp. The way it works now is that when a paper is uploaded to publish.iacr.org, the paper number is assigned then to be the next one in order. This is much like the paperid that is assigned when something is submitted to hotcrp. Unfortunately if we assign paperno differently, it has the potential to cause havoc with different people looking at the list of papers, because a reassignment of paperno will invalidate the view that someone has in their browser.
I think the only solution is to add a button that would be used after all papers have been uploaded to publish.iacr.org to reorder the paperno by the value of the paperid (in reality we would use the
submitted
value, since that is easier to sort on).The text was updated successfully, but these errors were encountered: