We need to keep the same value in a single place.

It happened that these fields didn't match in two conferences today.

I think the solution is to save a single value(timestamp) and then decide which timezone to use to render the deadline in the webfield. So we can avoid the inconsistency of the dates.

When creating the MetaReview stage the user should have the same option of picking the decision recommendations as you do in the Decision stage.

The acceptance invitation content value-radio should be updated to match the meta review.

Users sometimes enter the recruitment list like:

'Reviewer name <email@address>'.

We should support either both or one of them. But we need to add an input validation so this error doesn't occur in the process function.

Reference: https://openreview.net/logs/process?id=B1eTx3w8UH

In order to debug process functions, we should think in something that helps us to debug the process functions.

We could create an script that mocks that note, invitation, etc and executes the process function. So we can check syntax errors, etc.

It's unclear how the samples should be used and if any specific permissions are required for the user.

I tried installing openreview-py through pip and the run python samples/python/get-reviewers.py --baseurl https://openreview.net MIDL.io/2019/Conference/ But this led to empty results:

submissions:
[]
notes:
[]
Reviewers:

I would be interested in understanding what's wrong with how I am trying to use the tool.

https://github.com/iesl/openreview-scripts/blob/master/admin/conference-template/webfield/conf.template#L45

function renderConferenceHeader() {
  Webfield.ui.venueHeader({
    title: <<TITLE>>,
    subtitle: <<SUBTITLE>>,
    location: <<LOCATION>>,
    date: <<DATE>>,
    website: <<URL>>,
    instructions: null,  // Add any custom instructions here. Accepts HTML
//    deadline: '2017-06-06 17:00:00'
  });

date: should be the date of the workshop, not the deadline
deadline: should be an string saying "Submission Deadline: June 17th, 2017 5:00pm" using the human readable date param.

When you call the template you need to change the parameters:

https://github.com/iesl/openreview-scripts/blob/master/admin/generate-conference.py#L78

with open(directory + '/webfield/conf.html', 'w') as new_webfile, open(utils.get_path('./conference-template/webfield/conf.template',__file__)) as template_webfile:
	templatestring = template_webfile.read().replace('<<TITLE>>',"\"%s\"" % conference_title)
	templatestring = templatestring.replace('<<CONF>>',"\"%s\"" % conference)
	templatestring = templatestring.replace('<<SUBMISSION_NAME>>', submission_name)
	templatestring = templatestring.replace('<<SUBTITLE>>',"\"%s\"" % conference_subtitle)
	templatestring = templatestring.replace('<<LOCATION>>',"\"%s\"" % conference_location)
	templatestring = templatestring.replace('<<DATE>>',"\"%s\"" % human_duedate)
	templatestring = templatestring.replace('<<URL>>',"\"%s\"" % url)
	new_webfile.write(templatestring)

DATE: should be the date when the workshop starts
and add a new parameter for the duedate like HUMAN_DUE_DATE

The questions about readership of the decision notes is confusing. If you select public you can still not release to authors.

I think instead of three questions it should be one.
Who should be able to see the Decisions when they are posted:

• everyone
• only the paper's reviewers (and ACs if applicable)
• only the paper's authors, reviewers (and ACs if applicable)

The revisionProcess will create blind_submissions even if the submissions are still open.

When the group doesn't exist it throws an exception and the script stop.

Looking at files such as get-reviewers.py, it is apparent that the code relies on python2 (e.g. print statements).

Given that "Python 2.x will reach the end of its life on January 1st, 2020", it would be fantastic to make sure the code is compatible with python3.

At least check syntax errors

for ICLR.cc/2017/conference/paper##/reviewers, the readers shouldn't be "everyone", they should be only the people that can make assignments

then, store the actual email addresses/signatures in here, not the wrapper groups

If an invitation has been customized (ex: add a field), the customization will get overwritten if the PC changes the due date using a Stage button.

After deleting a comment or a review, it shows a faded version with a “Restore” button. When I press the button it appears that it was restored, but the next time I load the page it is still grayed out and has the "Restore” button instead of the delete or edit buttons.