Hacky but working version for downloading papers for a workshop#201
Hacky but working version for downloading papers for a workshop#201habernal wants to merge 1 commit into
Conversation
crux82
left a comment
There was a problem hiding this comment.
Thanks for contributing this!
It is useful to have a working OpenReview API v2 workaround documented. I would be hesitant to merge it into main as-is, though, because the script still contains hardcoded venue/user/password placeholders, workshop-specific assertions, debug output, fixed output paths, and broad exception handling. The requirements.txt pin to openreview-py==2.2.0 may also affect existing workflows.
I think this would be mergeable if it were turned into a general-purpose script with CLI arguments for venue/user/output paths, no hardcoded submission counts, no credentials in the source, cleaner error handling, and ideally no breaking dependency change unless needed. Alternatively, it could live under an experimental/ or examples/ directory with clear documentation that it is a temporary workaround.
|
I agree with all points you raise. The intention here was to share a hacked but working solution for the new OR API to get a workshop proceedings compiled, not to develop an updated version of aclpub2. |
I had problems with downloading papers for proceedings of our PrivateNLP 2026 workshop edition - all my workflows from 2025 and earlier (I used them for our workshops and lately for EMNLP 2025 demo track) that worked with aclpub2 out of the box do not work anymore; the reason is, I assume, some changes in the OR API, as I couldn't fetch any submissions in the first place.
So this is heavily vibe-coded version of or2papers.py which I made to work for downloading our workshop papers, such that I can build the proceedings.
I suggest the maintainers of the main repo to investigate whether the original or2papers still works for all (big conferences, workshops), and if some workshop publication chairs run into similar issues, they can use the this new temporary script - but this is not meant as a robust solution. I hacked this together on Sunday just to get the job done (proceedings) without really digging into OR API.