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
Bernstein has adopted the policy, similar to SfN, to allow for editing of abstracts for a few more days after the submission deadline. This requires a state where the creation of new abstracts is disabled, but existing abstracts can be unlocked, edited and submitted.
The text was updated successfully, but these errors were encountered:
a) I would suggest to add and use an additional conference admin flag edit_abstract. When this flag is set, users are able to edit their abstracts, even if the submission deadline has passed.
This comes with the downside of requiring a conference admin to manually remove this state again when the "after-submission" edit time has passed, but with the state-flow suggested in b) I think this would be not a large problem. The upside is, that we do not need to carry around another date, especially when looking at the policy that the submission deadline is usually changed and prolonged once or twice.
b) Looking at the state-flow I would suggest that users should only be able to edit their abstracts, when they are in the submitted state. When they are in the InReview, Accepted or Rejected state, users should not be able to edit them any longer and should contact a conference admin to ensure, that changes are not made after an admin has already checked an abstract.
Bernstein has adopted the policy, similar to SfN, to allow for editing of abstracts for a few more days after the submission deadline. This requires a state where the creation of new abstracts is disabled, but existing abstracts can be unlocked, edited and submitted.
The text was updated successfully, but these errors were encountered: