Admin Guide

OpenReview can be thought of as having two kinds of users:

• End users: These users (often academics, industrial researchers, students, or members of the public) primarily interact with OpenReview through the web interface to add content in the form of papers, reviews, and comments.
• Conference organizers and workflow engineers: Conference organizers interact with OpenReview through the Web API or Python API wrapper and toolkit. For large conferences, organizers sometimes employ dedicated workflow engineers to manage the conference's workflow.

This guide is intended to help conference organizers and workflow engineers get started with configuring a conference.

If you're interested in running your own conference with OpenReview, please contact us at [email protected] to register an account with administrator-level privileges.

Using the openreview-scripts repository

The openreview-scripts repository contains scripts, written mostly in Python, used for setting up and managing conference workflows.

Conference-specific scripts are found in the venues directory, and are organized by conference domain name and year.

For the first couple years of OpenReview's existence, workflow engineers tended to write one-off scripts that would perform various pieces of functionality. These scripts are left in the repository for record-keeping purposes, but may be out of date, and may not be maintained in the future.

As of Summer 2018, beginning with the ICLR 2019 Conference, we have started encouraging workflow engineers to store conference-specific information and functionality in a Python module. We recommend interacting with this module using a IPython/Jupyter Notebook to communicate with the OpenReview servers.

Example: ICLR 2019 directory structure

/venues
  /ICLR.cc
    /2019
      /python
        iclr19.py
        iclr19.ipynb

Workflow Guides

• Conference Setup
• Recruiting Reviewers
• Enable Revisions