How to create, change, and delete notes

Jump to:

1. Posting (Creating) a Note

To post a new Note, create a Note object with required fields, then use client_v2.post_note_edit().

Required fields include:

  • invitation: the invitation ID defining the note type (e.g., a submission, review, comment)

  • forum: the ID of the main submission this note belongs to (for replies)

  • signatures: who is posting (usually a profile ID)

  • readers: who can read this note

  • writers: who can modify the note

  • content: a dictionary of the note content fields (title, authors, review text, etc.)

Quickstart: Posting a submission with Python

Posting a submission with Python is typically reserved for testing venue workflows and changes.

PCs and Reviewers that are also authors of test submissions will be conflicted later on in the process. We recommend using test author profiles for the submission process.

Quickstart: Posting a desk rejection for submissions missing PDFs

PCs may want to programmatically desk-reject submissions that are missing PDF files once the submission deadline has passed. You can use the script below to do so.

Quickstart: Posting a Support Request Form With Python

While a support request form can most easily be submitted through the UI, some venues that have multiple deadlines a year and need to submit multiple venue requests with the same settings may find it easier to do this programmatically through the API. While most notes are posted with the API2 client, this note must be posted with the API 1 client.

2. Editing Notes

Editing notes in API2 is done the same way as creating notes, by posting a note edit with new values for the fields.

Quickstart: Update the readers of a note or field

One common edit to make in bulk to notes is updating the readers of a note. This can be done in the UI for common configurations, but if your venue needs further fine-grained control over readership (for example custom tracks, groups, etc), then you can use the Python Client to change the readers of any subset of notes programmatically. The following script will change the readers of a note or field within a note to the new list.

For more examples, see: how to hide/reveal fields.

3. Deleting Notes and fields

Deleting notes should be used with caution as most changes can be done by editing a note, and once deleted, changes can be difficult to recover. Typically, we recommend deleting notes only in the case of testing a venue workflow on the dev site. To delete a note, you would post a note edit that includes a value (in millisecond time) for the ddate field, which has a value of None by default. An example is below:

Quickstart: Remove a field from a submission

Removing fields from submissions should be done sparingly. Oftentimes, changing the readers of the field its sufficient (see above), but in the case that you want to remove a field entirely, you can use the approach below"

Quickstart: Posting, editing, and deleting a test review

  1. Posting a new review note:

  1. Editing an existing review note, you must specify the note ID.

You can get all reviews, get a specific review, or get all reviews for one submission to edit (below):

  1. Deleting a review note:

Last updated

Was this helpful?