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
For LMCS's tooling to be ported to the API, we would need some kind of endpoint that would allow us to update an article's status. For instance, one thing we often do is move an article from "Accepted" to "Copy ed.: waiting for author's final version" when requesting the paper password.
Would it be possible to add an endpoint that would allow us to perform such manipulations? We would specify a paper's identifier, the action to be performed, and the message to be sent to the author.
Ideally, we would also like to include the email address to be used in the "reply-to" header of the email. Currently, our tooling temporarily updates the email address of our machine account (via the web interface) before sending this message, so as to ensure that the author's replies are sent to the layout editor that triggered the request.
The text was updated successfully, but these errors were encountered:
For LMCS's tooling to be ported to the API, we would need some kind of endpoint that would allow us to update an article's status. For instance, one thing we often do is move an article from "Accepted" to "Copy ed.: waiting for author's final version" when requesting the paper password.
Would it be possible to add an endpoint that would allow us to perform such manipulations? We would specify a paper's identifier, the action to be performed, and the message to be sent to the author.
Ideally, we would also like to include the email address to be used in the "reply-to" header of the email. Currently, our tooling temporarily updates the email address of our machine account (via the web interface) before sending this message, so as to ensure that the author's replies are sent to the layout editor that triggered the request.
The text was updated successfully, but these errors were encountered: