arrow-left

All pages
gitbookPowered by GitBook
1 of 11

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Revision

The Revision button on the venue request form allows you to modify selections made in the support request form. There are also new fields, 'Additional Submission' and 'Remove Submission Options', which allow PCs to modify the submission form.

Use of the Revision button will overwrite any changes to the Submission invitation that were made through the invitation editor rather than through the venue request form.

Review Stage

hashtag
What it Does

The Review Stage creates paper groups and review invitations. It should be used to edit the Review form. Use of the Review Stage will overwrite any changes made to the Review Invitations through the Invitation Editor. It also sets the visibility of all existing and future reviews.

hashtag
When to Use it

The Review Stage should not be run until after the submission deadline, except in the case of public, single blind venues. They can begin the Review Stage before the submission deadline if they first run 'Post Submission Stage' to create paper groups.

hashtag
Options

chevron-rightReview Start Datehashtag
  • When Review Invitations will open for Reviewers, in GMT

  • Optional

chevron-rightReview Deadlinehashtag
  • When Review Invitations will close for Reviewers, in GMT

  • Required

chevron-rightMake Reviews Publichashtag
  • If yes, sets the readers of existing and future reviews to 'everyone'.

  • Required

chevron-rightRelease Reviews to Authorshashtag
  • If yes, sets the readers of existing and future reviews to include paper authors.

  • Required

chevron-rightRelease Reviews to Reviewershashtag
  • Sets the visibility of existing and future reviews.

  • Required

chevron-rightEmail Program Chairs About Reviewshashtag
  • Determines if PCs will be notified of future review submissions.

  • Required

chevron-rightReview Rating Field Namehashtag
  • Determines which field should be used to calculate the average "rating" on the PC console. You should enter a field that has been added via "Additional Review Form Options".

  • The selected field should have options that follow the format "number: description". For example, "1: Very poor".

chevron-rightReview Confidence Field Namehashtag
  • Determines which field should be used to calculate the average "confidence" on the PC console. You should enter a field that has been added via "Additional Review Form Options".

  • The selected field should have options that follow the format "number: description". For example, "1: Not confident".

chevron-rightAdditional Review Form Options hashtag
  • Adds or overwrites fields to the Review Form. Expects valid JSON surrounded by a single pair of curly braces {}. Read more about the accepted field types .

  • Optional

chevron-rightRemove Review Form Optionshashtag
  • Removes fields from the Review form. Expects a comma separated list of field names in lowercase.

  • Optional

Registration Stage

What it Does

The Registration Stage creates a registration task for reviewers (and ACs, if applicable).

When to Use it

The Registration Stage can be run an any point during your workflow, though it is usually enabled at the begining to collect information from reviewers and/or ACs. It can also be used to ask users to update their profiles and import their publications.

Options

If your venue has area chairs, you will see two registration buttons, one for reviewers and one for ACs. Each form will have the following fields:

Defaults to now

Will not work if submissions are not public

Will not work if 'Make Reviews Public' is selected while submissions are not public

Required

  • Defaults to "rating"

  • Required

  • Defaults to "confidence"

  • Defaults to default Review Form.

    Defaults to default Review Form.

    here
    chevron-rightRegistration Start Datehashtag
    • When the registration task will become active, in GMT

    • Optional

    • Defaults to now

    chevron-rightRegistration Deadlinehashtag
    • The soft deadline reviewers and/or area chairs will see, in GMT

    • Required

    chevron-rightRegistration Expiration Datehashtag
    • The hard deadline when the task will expire, in GMT

    • Required

    chevron-rightRegistration Namehashtag
    • The name you choose will appear as a button in the Registration page

    • Use underscores to represent spaces

    • Optional

    • Default: 'Registration'

    chevron-rightForm Titlehashtag
    • Title of the registration form

    • Required

    • Default: 'Reviewer Registration' or 'Area Chair Registration'

    chevron-rightForm Instructionshashtag
    • Instructions reviewers or area chairs will see when completing the task

    • Required

    chevron-rightAdditional Form Optionshashtag
    • Additional fields that can be added to the registration form. Expects a valid JSON surrounded by a single pair of curly braces {}. Read more about defining fields here.arrow-up-right

    • Optional

    • Defaults to

    chevron-rightRemove Form Optionshashtag
    • Fields to be removed from the default registration form

    • Optional

    How to Query

    To query all registration notes submitted to your venue, follow these instructions.

    default Registration Form

    Bid Stage

    What it Does

    The Bid Stage is a feature of the OpenReview Paper Matching system that allows reviewers to indicate their preference of which papers they would like to review and place bids. See Score Specificationarrow-up-right to see how bids are then converted into scores.

    When to Use it

    The Bid Stage should not be run until after the submission deadline, except in the case of public, single blind venues. For public and single-blind venues, the Bid Stage can be run before the submission deadline if they first run 'Post Submission Stage' to create paper groups.

    It is recommended that venues first run Paper Matching to compute conflict of interest before opening the Bid Stage, but this is not required. If the conflict of interest scores are taken into account, the reviewers' own papers will be excluded from their bid selections.

    chevron-rightBid Start Datehashtag
    • When the bidding invitation opens, time in GMT.

    • Optional (will open immediately if start date is not selected)

    chevron-rightBid Due Datehashtag
    • When bidding closes, time in GMT.

    • Required

    chevron-rightBid Counthashtag
    • The minimum number of bids required for the task to be complete.

    • Defaults to 50.

    Comment Stage

    hashtag
    What it Does

    The Comment Stage creates Comment Invitations for all submissions with custom participants. The Comment forms have a dropdown menu where users can select the intended readers of their comments.

    hashtag
    When to Use it

    Double blind venues can only run the Comment Stage after the submission deadline has passed. Single-blind venues can run the Comment Stage before the submission deadline if they first run Post Submission Stage.

    hashtag
    Options

    chevron-rightCommentary Start Datehashtag
    • When comment invitations will open for selected participants, in GMT

    • Optional

    chevron-rightCommentary End Date hashtag
    • When comment invitations will close for all participants, in GMT

    • Optional

    chevron-rightParticipantshashtag
    • Selection of who will have access to comment invitations

    • Required

    chevron-rightEmail Program Chairs About Official Commentshashtag
    • Determines whether PCs will be notified of each comment.

    • Required

    Post Decision Stage

    hashtag
    What it Does

    The Post Decision Stage updates the visibility and anonymity of submissions after decisions have been posted.

    hashtag

    Post Submission Stage

    hashtag
    What it Does

    The Post Submission Stage creates Paper groups and sets the readers of submissions accordingly. It also creates the anonymized versions of submissions, if applicable.

    hashtag

    Optional

    Defaults to now

    Defaults to never

    When to Use it

    The Post Submission Stage should be used when paper groups and blind copies need to be created. In general, this should be done:

    • After the Abstract Registration deadline to allow authors to revise their submissions

    • After the Submission Deadline to hide fields from authors or update submission readers

    • After the submission deadline has passed a second time after having been extended

    • When the readers of the submissions need to be updated

    chevron-rightForce hashtag
    • Whether or not blind submissions and paper groups should be created before the submission deadline.

    • Required

    chevron-rightHide Fieldshashtag
    • Fields that will be hidden from everyone except for Program Chairs and the Paper Authors. The fields should exactly match the field names in the submission invitation.

    • Optional

    • Defaults to only author identities

    chevron-rightSubmission Readershashtag
    • Who should see the submissions; changes readers of all submissions in bulk as soon as Post Submission is run.

    • Required

    When to Use it

    The Post Decision Stage will only appear after the Decision Stage deadline. If you have already successfully posted all decisions but the Post Decision Stage has not yet appeared, you can re-run the Decision stage to make the deadline earlier.

    chevron-rightRelease Submissions hashtag
    • Changes the visibility of submissions. The decisions must also be released if you would like to release the submissions by decision.

    • Required

    chevron-rightReveal Authorshashtag
    • Changes anonymity settings of submissions.

    • Required

    chevron-rightHome Page Tab Nameshashtag
    • Creates or overwrites decision tabs on the venue homepage. Valid JSON with keys matching the decision options expected.

    • Optional

    chevron-rightSend Decision Notificationshashtag
    • Select whether or not you would like to send notification emails to authors when you submit Post Decision Stage.

    • Required

    • Defaults to "No, I will send the emails to the authors."

    chevron-right____ Email Content hashtag
    • Takes a template decision notification for each decision type for your venue. If "Yes, send an email notification to the authors" was selected, these templates will be populated with the paper information and sent to the authors of the respective papers.

    • Optional

    • Defaults to the

    Ethics Review Stage

    hashtag
    What it Does

    The Ethics Review stage is available to any venue that selected "Yes, our venue has Ethics Chairs and Reviewers" on their venue request form. Running the Ethics Review stage will create Paper#/Ethics_Reviewers groups and Ethics Review Form invitations for each flagged paper.

    hashtag
    When to Use It

    The Ethics Review Stage can be run at any time after the Submission Deadline for Double Blind conferences and any time after Post Submission Stage is run for Single Blind conferences. It can be run multiple times with different paper selections; if you run it again, excluding a paper that was originally flagged, that paper will be removed unless it already has an ethics reviewer assigned to it. The flagged papers list must always contain all of the papers that should be flagged for ethics review.

    chevron-rightEthics Review Start Datehashtag
    • When ethics reviewers can start writing their reviews, in GMT

    • Optional

    chevron-rightEthics Review Deadline hashtag
    • When the ethics review invitations expire, in GMT

    • Required

    chevron-rightMake Ethics Reviews Publichashtag
    • Whether the ethics reviews should be made immediately public. Only available if submissions are public.

    • Required

    chevron-rightRelease Ethics Reviews to Authorshashtag
    • Whether the ethics reviews should be made immediately available to the authors.

    • Required

    chevron-rightRelease Ethics Reviews to Reviewers hashtag
    • Which reviewers and ethics chairs the reviews should be immediately released to

    • Required

    chevron-rightEthics Review Submissionshashtag
    • A comma-separated list of the paper numbers of submissions requiring ethics review.

    • Required

    chevron-rightAdditional Ethics Review Form Optionshashtag
    • Additional options that will be added to the default Ethics Review Form. Expects valid JSON surrounded by a single pair of curly braces {}. Read more about the accepted field types .

    • Optional

    chevron-rightRemove Ethics Review Form Options hashtag
    • Removes fields from the Review form. Expects a comma separated list of field names in lowercase.

    • Optional

    Submission Revision Stage

    hashtag
    What it Does

    The Submission Revision Stage creates invitations that allow authors to revise their original submissions.

    hashtag

    When to Use it

    Double blind venues can only run the Submission Revision Stage after the submission deadline has passed. Single-blind venues can run the Submission Revision Stage before the submission deadline if they first run Post Submission Stage.

    chevron-rightSubmission Revision Namehashtag
    • The name you choose will appear as a button on the forum of each revisable submission.

    • Optional

    • Default: 'Revision'

    chevron-rightSubmission Revision Start Date hashtag
    • When the Revision invitation should open for authors, in GMT.

    • Optional

    • Default: now

    chevron-rightSubmission Revision Deadlinehashtag
    • When the Revision invitation will close for authors, in GMT.

    • Required

    chevron-rightAccepted Submissions Only hashtag
    • Whether or not revisions should be allowed for only accepted submissions.

    • Required

    chevron-rightSubmission Revision Additional Options hashtag
    • Additional options that can be added to submissions. Expects valid JSON surrounded by a single pair of curly braces {}. Read more about the accepted field types here.

    • Optional

    • Default options for revision are all fields of the Submission Form.

    chevron-rightSubmission Revision Remove Optionshashtag
    • Fields that the authors will not be able to edit. Expects a comma separated list of field names in lowercase.

    • Optional

    • Default options for revision are all fields of the Submission Form.

    default decision notification

    Defaults to now

    Defaults to the default Ethics Review Form

    Defaults to default Ethics Review Form.

    here

    Decision Stage

    hashtag
    What it Does

    The Decision Stage creates decision invitations for Program Chairs. Use of the Decision Stage will overwrite any changes made to the Decision Invitations through the Invitation Editor. It will also overwrite any customized readership settings that were not made through the venue request form.

    hashtag
    When to Use it

    The Decision Stage should not be run until after the submission deadline, except in the case of public, single blind venues. They can begin the Decision Stage before the submission deadline if they first run 'Post Submission Stage' to create paper groups.

    chevron-rightDecision Start Datehashtag
    • When Decision Invitations open for Program Chairs, in GMT.

    • Optional

    chevron-rightDecision Deadlinehashtag
    • When decisions will close for Program Chairs, in GMT.

    • Required

    chevron-rightDecision Options hashtag
    • Decision types. Expects comma-separated list

    • Optional

    chevron-rightMake Decisions Publichashtag
    • If yes, sets the readers of existing and future decisions to 'everyone'.

    • Required

    chevron-rightRelease Decisions to Authorshashtag
    • If yes, sets the readers of existing and future decisions to include paper authors.

    • Required

    chevron-rightRelease Decisions to Reviewershashtag
    • Sets the visibility of existing and future Decisions.

    • Required

    chevron-rightRelease Decisions to Area Chairs hashtag
    • Sets the visibility of existing and future Decisions.

    • Required

    chevron-rightAdditional Decision Form Optionshashtag
    • Adds or overwrites fields to the Decision Form. Expects valid JSON surrounded by a single pair of curly braces {}. Read more about the accepted field types .

    • Optional

    chevron-rightDecisions Filehashtag
    • Allows for bulk upload of decisions. Expects a csv containing the paper_id, decision, and comment for one paper per line. Does not expect a header/column names. The comment column is optional.

    • Optional

    Defaults to now

    Defaults to "Accept (Oral)", "Accept (Poster)", "Reject"

    Will not work if submissions are not public

    Will not work if 'Make Decisions Public' is selected while submissions are not public

    Defaults to

    Defaults to manual Decisions.

    here
    default Decision Form

    Stages