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
At the moment, selecting "Corrections Required" on the "Review Typesetting" screen simply closes the current typesetting assignment. Similarly, selecting "Request Corrections" on the "Typesetting Article #" page simply opens a new (blank) typesetting round.
Instead, I would personally prefer that selecting "Corrections Required" do the following:
(a) close the current typesetting assignment,
(b) start a new typesetting round, and
(c) create a new assignment that's automatically assigned to the same typesetter as the previous one.
(I was also entertaining the idea that "Corrections Required" could "re-open" the existing typesetting assignment, within the same round, so that feedback can be sent back to the typesetter for incorporation into a revised PDF/XML--basically the same workflow currently used in Copyediting. Though perhaps this is too dramatic of a change to the plugin's base functionality?)
The text was updated successfully, but these errors were encountered:
At the moment, selecting "Corrections Required" on the "Review Typesetting" screen simply closes the current typesetting assignment. Similarly, selecting "Request Corrections" on the "Typesetting Article #" page simply opens a new (blank) typesetting round.
Instead, I would personally prefer that selecting "Corrections Required" do the following:
(a) close the current typesetting assignment,
(b) start a new typesetting round, and
(c) create a new assignment that's automatically assigned to the same typesetter as the previous one.
(I was also entertaining the idea that "Corrections Required" could "re-open" the existing typesetting assignment, within the same round, so that feedback can be sent back to the typesetter for incorporation into a revised PDF/XML--basically the same workflow currently used in Copyediting. Though perhaps this is too dramatic of a change to the plugin's base functionality?)
The text was updated successfully, but these errors were encountered: