Code Monkey home page Code Monkey logo

aclrollingreview's People

Contributors

ajstent avatar amitmerchant1990 avatar annargrs avatar codogogo avatar cryptexcode avatar dongqi-me avatar ecekt avatar ehudreiter avatar handecelikkanat avatar hungyilee avatar ipavlopoulos avatar jkkummerfeld avatar lbiester avatar leondz avatar mayhewsw avatar mcdm avatar neubig avatar nschneid avatar riedelcastro avatar sarahwie avatar sdobnik avatar sebastinsanty avatar sigdialwebadmin avatar sm354 avatar sophiehenning avatar sstoyanchev avatar svivek avatar texttheater avatar thamar-solorio avatar timabell avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

aclrollingreview's Issues

Clarifications regarding resubmissions

From @nschneid:

  • What about resubmissions? Is it important to assign the original reviewers if possible (or is it OK to replace, for example, a positive but less informative reviewer)? Note that the platform provides access to the new paper as well as authors' summary of changes. Any other special considerations for handling resubmissions?

Reviewer names are revealed to other reviewers

(moved from openreview/openreview#15 )

Describe the bug
I'm not sure if this is intentional or not, but as as reviewer, I can see other reviewers' names, e.g.:

ACL ARR 2022 January PaperXXX Reviewer XXX FirstName SecondName (privately revealed to you)

Expected behavior
I believe reviewers should stay anonymous among themselves. I don't see any reason for doing otherwise. Maybe double-check with ARR editors.

melisabok commented 2 hours ago
It seems the ARR organizers specified this, please check with the ARR organizers.

Add a login button or link

Is your feature request related to a problem? Please describe.
Is there a login link on the home page? I cant find it. It's frustrating to find where to login for reviewing. Adding a Login link at *the top would be helpful.
image

Describe alternatives you've considered
Alternative is to memorize that I need to login to Openreview.net not aclrollingreview.org

Per-paper COIs and nominated reviewers

Summary

I think that there's a need for identifying reviewers who would have a conflict of interest in reviewing a submission (but whom you don't have a general COI with).
Also, it would make sense to implement structure to nominate reviewers who would be particularly well-suited to review a submission. This is a pretty common interface in a lot of social scientific research venues to help guide reviewer selection.

Per paper COIs

It can be relevant with per-paper COIs for instance in cases where authors are directly addressing issues with other authors' work or where some specific reviewers would have a vested interest in seeing those papers not be published (disproves, refutes, highlights issues or is competing in time with the would-be COIs work).
This would be on a per-paper basis, it isn't a matter of relationship between authors but between reviewers and submitted paper.

Per-paper nominated reviewers

This can be useful, particularly for new tasks/methods/theories that are introduced into the ACL community, where it is unclear who a good reviewer is, even to a well informed AE or SAC (if submitted at conference deadline time). In these cases, it could serve as an aid to AEs and SACs in selecting reviewers if some reviewers are already nominated, as AEs and SACs can select reviewers whose body of work/profile is similar to that of the nominated reviewers, if the nominated reviewers aren't available or there's a COI.

Suggested nav bar reorg

It currently looks like this:
image

The way it wraps across lines is ugly.

Moreover,
a) not all users are necessarily familiar with what "CFP" stands for
b) there is a separation of Reviewers vs. AEs, but nothing about SAEs
c) The vast majority of visitors will be authors, so it is perhaps unnecessary to devote a huge chunk of the navbar to "Reviewers" "Action Editors" "Venue Organizers"

How about:
image
where "Review Team" is a catch-all for the various roles, including venue PCs. One page would explain the different roles and link to further information.

What do you think?

Clarifications regarding reviewer discussion

Questions from @nschneid:

  • Is it recommended to always open the floor for discussion, or just when there is disagreement among reviews?
  • Are there things AEs should be on the lookout for that would be inappropriate in reviews, and ask the reviewers to edit? E.g. vague criticisms (ask the reviewer to be more concrete), overly harsh tone....

Unclear whether authors can see discussions between reviewers and AC

Reviews will be made accessible to authors after the "review release" date. However, I don't know whether it is true also for any threads (discussions) between reviewers and ACs.

For example, this is the original review (with some group access rights which do not contain authors yet, I guess?)

s_2022-02-22_13-26-11

And here is my answer to the review as AC where I tried to clarify some potential misunderstandings:

s_2022-02-22_13-28-02

Both have the same access groups now, but will they all be released to the authors? (which would be favorable, as they add more transparency to the decision process)

Make link to paper style files easier to find

Currently the style files are accessed by clicking (taking the LaTeX style file as an example):

"CFP" -> "here" -> "latex" -> "acl.sty"
"Authors" -> "Submission templates" -> copy and paste URL -> "latex" -> "acl.sty"

I would be happy to make the link at https://acl-org.github.io/ACLPUB/formatting.html clickable. I'd also be happy to make a PR here, but want to know if there are any guidelines to follow. For example, do we want there to be a single entry point, and if so, should it be https://acl-org.github.io/ACLPUB/formatting.html or https://github.com/acl-org/acl-style-files?

@mjpost

Permanent Unavailability to review

Authors should be provided with the option to never be available to review for ARR under specific conditions.
For instance, authors who are not within the NLP field are unlikely to be qualified reviewers for a majority of submitted papers.
To account for such instances, the review unavailability form should include an option to indicate that although one has submitted work to ARR (as a co-author most likely), one is not qualified to review.

The lack of such a possibility creates unnecessary barriers to interdisciplinary work to appear in ACL venues.

Currently, the only possibility to mark yourself as not qualified to review is marking yourself as unavailable far into the future - which subverts the purpose of unavailability form.

Area Chair console does not show AC Recommendation scores

See the screenshot. I would expect that "AC Recommendation:" would display the given score (which is called "Overall Assessment" in the meta review), for example

"AC Recommendation: 3" or better "AC Recommendation: 3 (There are major points that may be revised)"

s_2022-02-23_10-30-42

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.