Add Compatability with API2

[haroldrubio]

This PR adds support for API2 by making the following changes to:

or2papers.py

• Initializes an API2 client
• Handles deprecation of query by notes with non-prefix invitation regex by fetching replies in details
• Adds separate logic for publication chairs vs program chairs
• Fetch content field depending on API version

or2program_committee.py

• Initializes an API2 client
• Handles deprecation of query by groups with non-prefix invitation regex by loading all conference groups and filtering as a post-process step

[zhzhang]

Is there a reason to keep the original client around? All venues going forward will be on the v2 API no?

[haroldrubio]

I left support for the original client in just in case the scripts need to be re-run on older venues - but if this isn't really a common use case and is just for use with new venues then it could be completely removed

[zhzhang]

I see! I don't think it will be a common use case, would you be able to refactor this PR to only use the v2 API? Thanks!

[zhzhang]

One additional question: I'm trying to run this updated script for EACL 2024. Is the correct venue string eacl.org/EACL/2024/Conference or EACL/2024/Conference? I'm able to get past the venue group validation, but the list of submissions pulled is empty. Not sure if this is an issue with the conference, or with me not having the right program chair permissions, or some other problem.

[crux82]

@haroldrubio thank you for your great job!

Here are some additional issues, just to keep track:

• Currently, as Publication Chair, I cannot download the Program Committee (and it's unclear why; OpenReview simply returns an empty list).
• I can download papers but some metadata are not included in the file paper.yml
  • I am unable to distinguish findings from long/short papers accepted in the main conference. Among the metadata, there is a decision field that is currently null, but I expect it to have values like "Accept to main conference" or "Accept to findings."
  • The abstract field is an empty string. It's necessary for the ACL Anthology, Underline, and (possibly) the handbook.
  • The submitted_area attribute is set to null. It's not necessary for the proceedings, but it has been very useful in the past for creating the program (to group papers into thematic sessions, with Jordan's program builder).

Thank you again!

Danilo

[haroldrubio]

@zhzhang The correct string is eacl.org/EACL/2024/Conference. The submissions list should be empty because the submissions are only visible to their assigned program committees and the publication and program chairs.

I'll also work on refactoring the code to only use API2

[haroldrubio]

eacl.org/EACL/2024/Workshop/DravidianLangTech/ is not working

python or2papers.py bharathiraja.akr@gmail.com ***** eacl.org/EACL/2024/Workshop/DravidianLangTech/ output eacl.org/EACL/2024/Workshop/DravidianLangTech/ not found

Your venue string has a trailing /, it should work if you trim that character off: eacl.org/EACL/2024/Workshop/DravidianLangTech

[haroldrubio]

I've added some error parsing, can you run it again for your workshop(s) and show me the error now?

[haroldrubio]

While you're in the aclpub2 directory, you should be able to use git pull to get the latest changes

[crux82]

@bharathichezhiyan as publication chair of EACL I downloaded this material and will upload in your github repository

[crux82]

@haroldrubio: when downloading the PDFs and attachments (using --all --pdfs), I get this error.

Traceback (most recent call last):
  File "/Users/danilo/progetti/aclpub2/openreview/or2papers.py", line 192, in <module>
    main(args.username, args.password, args.venue, args.all, args.pdfs)
  File "/Users/danilo/progetti/aclpub2/openreview/or2papers.py", line 143, in main
    file_tye = get_content_from(submission, "software").split(".")[-1]

I think it is a problem parsing the metadata of the attachments

Can you please fix it?

[crux82]

@haroldrubio the download of the attachments works. I just fixed a problem about the naming of attachments.

If we could also download the reviewers, we would be all set :-)

[haroldrubio]

@crux82 When I run the committee script, it appears to list the reviewers in the YML file after the line role: Area Chairs. Is this the case for you or are you running into something else with the reviewers?

[crux82]

@haroldrubio I am sending you what I downloaded via mail

[crux82]

@haroldrubio any news?