Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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}}
, {{firstname}}
Frontend tags: [[SUBMIT_REVIEW_LINK]]
If you want to include further customizations, including links to papers or reviews, you can
You can send messages through OpenReview using the python client post_message function. You will first need to install and setup the python client. Your recipients could be a list of OpenReview profile IDs, a list of email addresses, or an OpenReview group ID. The important thing is that whichever ID you use for the recipient, it has to be a member of a group you are a writer of. This property is called the parentGroup
. This is how OpenReview gives permission to organizers to send emails. If you do not know what the corresponding group of your recipient is, you can find it with the following query:
This will return a JSON with the property id
and details.writable
. If a group has details.writable=true
, that group id
can be used as your parentGroup
.
To send a message to all of your venue's authors, or example:
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. If your venue is single blind, replace /-/Blind_Submission with /-/Submission:
If your venue is set up to use API 1, and the submission deadline has not passed then you can send a message to submission authors by doing the following:
If you don't know what API version you're using, you can check this by viewing your venue request form, look for the field "API Version". If there is no such field on your venue request form you are using API 1 by default.
The Author group is not populated until after the submission deadline, so until then, there is not a way to message authors through the User Interface. You can send messages to authors through OpenReview using the python client.
In API 2, the Author groups will be populated before the deadline.
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. 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 Post Decision multiple times, it will send the decision notifications each time that "Yes, send an email notification to the authors" is selected. If you need to make changes to Post Submission stage without sending out emails each time, make sure to select "No, I will send the emails to the authors".
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.
Since the Submissions do not contain the decisions, we first need to retrieve all the Decision notes, filter the accepted notes and use their forum ID to locate its corresponding Submission. We break down these steps below.
Retrieve Submissions and Decisions:
It is convenient to place all the submissions in a dictionary with their id as the key so that we can retrieve an accepted submission using its id.
We then filter the Decision notes that were accepted and use their forum ID to get the corresponding Submission:
You can then message the author ids of each accepted submission.
This is very similar to the previous example. The only difference is that we need to get the blind notes with the added details parameter to get the Submission.
Retrieve Submissions and Decisions:
We then filter the Decision notes that were accepted and use their forum ID to get the corresponding Submission:
You can then message the author ids of each accepted submission.
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.