Posting a Test Submission
If you are testing your venue on the dev site, you may want to generate some test submissions. This can be accomplished manually through the UI, but it may be faster to do it with python using the guide below.
Venues using API V1
If you have not already, you will need to create a username and password on the dev site: dev.openreview.net/signup. Note that sending emails through the dev site is not supported. Therefore, you will need to request the activation link at info@openreview.net.
Instantiate the python client using your dev profile credentials:
Familiarize yourself with the submission invitation. Every content field of your note will need to be in the format specified by the submission invitation, and any fields marked as "required" will need to be present in the note.
Create your note. If you were submitting a note through the default submission form, it would look something like this:
Invitation: The ID of your venue's submission invitation. It will take the form of your venue id + /-/Submission. Readers/Writers: A list of the venue ID + all author profile IDs. After the submission deadline, these values will be automatically updated to match the visibility settings selected in the venue request form. Signatures: Your profile ID. Content: The actual content of the submission, which must match the invitation. If the invitation calls for any file uploads, such as a pdf or zip file, you can build the url to the file using put_attachment and entering the path, the invitation ID, and the name of the field. You can then add that field to the note's content. The "authorids" field of the note's content should contain a list of the authors' profile IDs or emails, in the same order as the authors' names. If you registered dummy users, you can find their profile IDs by going to their profile page and copying the ID parameter of that page's url. For example, dev.openreview.net/profile?id=~Test_Author2 --> ~Test_Author2.
Post your note and output the resulting note's ID:
You can now view your note in the UI by going to dev.openreview.net/forum?id=<note_id>.
Venues using API V2
If you have not already, you will need to create a username and password on the dev site: dev.openreview.net/signup. Note that sending emails through the dev site is not supported. Therefore, you will need to request the activation link at info@openreview.net.
Instantiate the python client using your dev profile credentials:
Familiarize yourself with the submission invitation. Every content field of your note will need to be in the format specified by the submission invitation, and all the fields that do not contain
optional: true
are mandatory.Create your note. If you were submitting a note through the default submission form, it would look something like this:
Invitation: The ID of your venue's submission invitation. It will take the form of your venue id + /-/Submission. Readers/Writers: A list of the venue ID + all author profile IDs. After the submission deadline, these values will be automatically updated to match the visibility settings selected in the venue request form. Signatures: Your profile ID. Content: The actual content of the submission, which must match the invitation. If the invitation calls for any file uploads, such as a pdf or zip file, you can build the url to the file using put_attachment and entering the path, the invitation ID, and the name of the field. You can then add that field to the note's content. The "authorids" field of the note's content should contain a list of the authors' profile IDs or emails, in the same order as the authors' names. If you registered dummy users, you can find their profile IDs by going to their profile page and copying the ID parameter of that page's url. For example, dev.openreview.net/profile?id=~Test_Author2 --> ~Test_Author2.
Post your note and output the resulting note's ID:
You can now view your note in the UI by going to dev.openreview.net/forum?id=<note_id>.
Last updated