A guide for program chairs on how to customize the different forms available to the reviewing committee
Where to customize forms
Many OpenReview forms are customizable from the different buttons on the venue request form. You can find where to input your customizations by clicking on a button (for example, "Review Stage") and finding the large text box under "Additional _____ Options". Under "Revision", you'll find that this box modifies the submission form under the heading "Additional Submission Options". For the "Review Stage", the heading will be "Additional Review Form Options"
Some buttons configure other parts of the workflow that do not have an associated form, in which case there will not be an additional options text box.
Whenever possible, forms should be customized through the venue request form following the directions above rather than editing an invitation directly - this saves your changes in the case that you update any other settings for your venue.
Essential structure of custom fields
These text boxes accept a valid JSON object with fields and values. The following is an example where the title field gets replaced with a radio button, like so:
When making a field that is asking for user input, you will always see this pattern of "value": { "param": {...} }. Inside the param object are fields determining what the user sees in the input form along with what the user is allowed to submit: these are representation specifiers and validation specifiers.
Both validation and representation specifiers can be found inside the param object
Specifiers
This section will introduce common specifiers used in customizing forms. Further information about specifiers can be found here.
Representation Specifiers
Representation specifiers determine how the user will input their response into the field (for example a textbox or a checklist). These will be defined in the param object.
The input specifier determines the rendering on the form and can have the following values (see below for examples of how different input types render):
text
select
checkbox
textarea
radio
default is the default value of the box that will appear when the widget is initialized
markdown is a boolean value (true/false) that enables markdown for this text field
scroll is a boolean that adds a scroll bar to a textarea input
Validation Specifiers
Validation specifiers are used by the back-end to ensure data submitted through the form conforms to certain requirements. In the example above, only a single string is allowed, and that string must be one of the values defined in the enum array. Specifically, a string that has the value "Test Submission Title"
optional is a boolean (true/false) value that indicates whether or not this field is required to be present when the form is submitted. By default all fields in the form are required, and you can add optional : true to indicate a required field.
Required fields have their field names prefixed with an asterisk
type specifiers require the input to be of a specific type: options are string, string[] (string array) and file.
string fields can be further validated by using fields to describe the structure of a valid string input. Some of these field are:
"maxLength": set the maximum number of characters of the input
"minLength":set the minimum number of characters of the input
"regex": use regular expressions to define acceptable string structures
"enum": restrict the user to a predefined set of strings (usually used with type: string[])
file fields are specifically validated with maxSize and extensions. maxSize is an integer that specifies the size of the largest file that can be uploaded on the form in megabytes. extensions is a list of strings that are extensions, for example "extensions": ["pdf", "zip"].
Extensions that have a "." in them are not supported. The following field would be invalid because "tar.gz" is not supported:
{
"comment": {
"order": 2,
"description": "Your comment or reply (max 5000 characters). Add formatting using Markdown and formulas using LaTeX. For more information see https://openreview.net/faq",
"value": {
"param": {
"type": "string",
"maxLength": 5000,
"markdown": true,
"input": "textarea"
}
}
}
}
Single Choice
{
"recommendation": {
"order": 10,
"description": "Please provide your recommendation based on the manuscript, reviews, author responses and your discussion with the reviewers.",
"value": {
"param": {
"type": "string",
"enum": [
"Reject",
"Accept",
"Nominate for best paper"
],
"input": "radio"
}
}
}
}
{
"submission_track": {
"order": 11,
"description": "Please select a preferred track, which will be considered in the paper-reviewer assignment. Please note that your choice of a track will be taken into account, but the chairs may decide to move your paper to a different area when appropriate.",
"value": {
"param": {
"type": "string",
"enum": [
"Commonsense Reasoning",
"Computational Social Science and Cultural Analytics",
"Dialogue and Interactive Systems",
"Discourse and Pragmatics",
"Efficient Methods for NLP",
"Ethics in NLP",
"Human-Centered NLP",
"Information Extraction",
"Information Retrieval and Text Mining",
"Interpretability, Interactivity, and Analysis of Models for NLP",
"Language Grounding to Vision, Robotics and Beyond",
"Language Modeling and Analysis of Language Models",
"Linguistic Theories, Cognitive Modeling, and Psycholinguistics",
"Machine Learning for NLP",
"Machine Translation",
"Multilinguality and Linguistic Diversity",
"Natural Language Generation",
"NLP Applications",
"Phonology, Morphology, and Word Segmentation",
"Question Answering",
"Resources and Evaluation",
"Semantics: Lexical",
"Semantics: Lexical, Sentence level, Document Level, Textual Inference, etc.",
"Sentiment Analysis, Stylistic Analysis, and Argument Mining",
"Speech and Multimodality",
"Summarization",
"Syntax, Parsing and their Applications",
"Theme Track: Large Language Models and the Future of NLP"
],
"input": "select"
}
}
}
}
Multiple Choices
{
"confirmation_of_submission_requirements": {
"order": 17,
"description": "Before you submit this paper, please make sure that the following requirements are met. If any of these requirements are not fulfilled, your submission will be rejected and will not be reviewed.",
"value": {
"param": {
"type": "string[]",
"optional": true,
"enum": [
"Requirement 1",
"Requirement 2"
],
"input": "checkbox"
}
}
}
}
{
"submission_tracks": {
"order": 11,
"description": "Please select your preferred tracks, which will be considered in the paper-reviewer assignment. Please note that your choice of tracks will be taken into account, but the chairs may decide to move your paper to a different area when appropriate.",
"value": {
"param": {
"type": "string[]",
"enum": [
"Commonsense Reasoning",
"Computational Social Science and Cultural Analytics",
"Dialogue and Interactive Systems",
"Discourse and Pragmatics",
"Efficient Methods for NLP",
"Ethics in NLP",
"Human-Centered NLP",
"Information Extraction",
"Information Retrieval and Text Mining",
"Interpretability, Interactivity, and Analysis of Models for NLP",
"Language Grounding to Vision, Robotics and Beyond",
"Language Modeling and Analysis of Language Models",
"Linguistic Theories, Cognitive Modeling, and Psycholinguistics",
"Machine Learning for NLP",
"Machine Translation",
"Multilinguality and Linguistic Diversity",
"Natural Language Generation",
"NLP Applications",
"Phonology, Morphology, and Word Segmentation",
"Question Answering",
"Resources and Evaluation",
"Semantics: Lexical",
"Semantics: Lexical, Sentence level, Document Level, Textual Inference, etc.",
"Sentiment Analysis, Stylistic Analysis, and Argument Mining",
"Speech and Multimodality",
"Summarization",
"Syntax, Parsing and their Applications",
"Theme Track: Large Language Models and the Future of NLP"
],
"input": "select"
}
}
}
}
Miscellaneous
{
"supplementary_material": {
"order": 10,
"description": "All supplementary material must be self-contained and zipped into a single file. Note that supplementary material will be visible to reviewers and the public throughout and after the review period, and ensure all material is anonymized. The maximum file size is 200MB.",
"value": {
"param": {
"type": "file",
"extensions": [
"zip",
"pdf",
"tgz",
"gz"
],
"maxSize": 200,
"optional": true
}
}
}
}
Setting the Readers of a Field
If you want to limit who in the committee can see a particular field in a form, this is done by adding a readers field. Please follow this link for more detailed information on hiding or revealing fields. Below are two examples, one for the submission form and one for the meta review form. Notice the different use of dollar sign notation. The notation used for the meta review form will also work for other replies to the forum: reviews, comments, and decisions.
{
"supplementary_material": {
"order": 10,
"description": "All supplementary material must be self-contained and zipped into a single file. Note that supplementary material will be visible to reviewers and the public throughout and after the review period, and ensure all material is anonymized. The maximum file size is 200MB.",
"value": {
"param": {
"type": "file",
"extensions": [
"zip",
"pdf",
"tgz",
"gz"
],
"maxSize": 200,
"optional": true
}
},
"readers": [
"Your/Venue/ID/Program_Chairs",
"Your/Venue/ID/Submission${4/number}/Senior_Area_Chairs",
"Your/Venue/ID/Submission${4/number}/Authors"
]
}
}
{
"recommendation": {
"order": 10,
"description": "Please provide your recommendation based on the manuscript, reviews, author responses and your discussion with the reviewers.",
"value": {
"param": {
"type": "string",
"enum": [
"Accept (Oral)",
"Accept (Poster)",
"Reject"
],
"input": "radio"
}
},
"readers": [
"Your/Venue/ID/Program_Chairs",
"Your/Venue/ID/Submission${7/content/noteNumber/value}/Area_Chairs",
"Your/Venue/ID/Submission${7/content/noteNumber/value}/Reviewers"
]
}
}
