Program Chairs can message any venue participants through the group consoles. Clicking any of the links under 'Venue roles' on your PC console will bring you to a console for that group. If you click 'Edit group', you will see the option to email those group members. You can customize the emails using the backend tags. Note that you will not be able to use the author group to message authors until after the submission deadline.
You can use the PC console Paper Status, Reviewer Status, or Area Chair Status tabs to message selected reviewers or area chairs, respectively. You will also have the option to message only those with incomplete reviews/metareviews, only those with completed reviews/metareviews, or only those assigned to particular papers. You can customize the emails using either the frontend or backend tags.
Emails can be sent to users of your venue programmatically using the API or from certain pages like the Program Chair console. They can be personalized to include the recipient's name or other information using email template tags.
There are two types of email template tags: Tags that are handled on the backend by the OpenReview API, and tags that are replaced on the frontend (in the browser).
Backend tags can be used anywhere, including when sending messages directly using the API or via the openreview-py library. Frontend tags can only be used on specific pages, such as the Area Chair console and the Program Chair console. A list of all available tags is below:
Backend tags: {{fullname}}
Frontend tags: [[SUBMIT_REVIEW_LINK]]
If you want to include further customizations, including links to papers or reviews, you can message users with the python client.
You can send messages through OpenReview using the python client post_message function. You will first need to install and setup the python client.
To send an email you need:
subject: Subject line of the email
message: Text of the email
recipients: List of OpenReview profile IDs, email addresses, or OpenReview group IDs.
invitation: An invitation that allows you to send an email to your recipients (this is usually the meta invitation invitation for venue organizers).
Below are some examples of common cases for sending emails.
If you wanted to include a link to each author's paper in the email, you could instead iterate through each submission and send an email with the papers' authorids fields as recipients:
After the decision stage closes, you will see the Post Decision Stage option on your venue request form. You will be able to use this stage to send bulk decision notifications to authors.
Select "Yes, send an email notification to the authors" for the "Send Decision Notifications" field.
Customize the Email Content Fields. There should be one per decision type for your venue. Do not remove the parenthesized tokens. Any fields in curly braces will be populated with the information for each paper. You can customize anything in the message so long as you do not remove the curly braces.
Click submit and notification emails will be sent to all authors.
Note that if you run the Post Decision Stage multiple times, new decision notifications will not be sent again even when "Yes, send an email notification to the authors" is selected. To re-send decision notifications, you should use the python client.
Go to https://openreview.net/messages. You should see any messages sent from your venue.
Filter messages by Parent Group to narrow your search:
If you sent a message through a group console, enter that group ID.
If you sent a message through the python client and specified the parent group, search by that parent group.
If you sent a message through the PC console, there will not be a parent group.
You can also filter by recipient, email status, and subject.
Under the ‘Overview’ tab of the PC console for your venue, you will find a ‘Venue Roles’ section. Click on the ‘Accepted’ link next to ‘Authors’ to be taken to the Accepted Authors group. On this page, click 'Edit group'. You will then have the option to email members of the group.
This option will work for use cases that do not need to customize messages. If you want to customize messages or have more control over who the recipient is, then please use the python client.
PCs can utilize the python client to send customized messages or to a more controlled recipient group. Three different use cases are outlined below. All use cases assume that PCs have already run the Post Decision Stage.
First, you will need to get all of the accepted submissions for your venue.
Second, loop through the submissions and for each submission send an email using the authorids
in the submission.content. This message will be sent to all the authors of the submission.
Unless you added a field to the submission form that required authors to indicate the corresponding author, OpenReview does not indicate which author in the list is the corresponding author.
If you want to email the author listed first in the submission, you can do this:
To start, get all the accepted submissions for your venue, like in the sections above, except this time include the param details='replies'
.
Stored in the submission.details retrieve the replies that contain the Decision invitation.
Retrieve the decision notes for a specific decision. For this example, I will use 'Accept (Proceedings)', please change this to match the specific value in the decision note:
Now that the decision notes have been filtered by the decision, we need the corresponding submission note to get the submission information.
You can then message the author ids of each accepted submission either using the SubmissionX/Authors group or the authorids like in the previous examples.