Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore duplicate entries in the order file #39

Open
mjpost opened this issue Jun 19, 2020 · 4 comments
Open

Ignore duplicate entries in the order file #39

mjpost opened this issue Jun 19, 2020 · 4 comments
Assignees

Comments

@mjpost
Copy link
Member

mjpost commented Jun 19, 2020

ACLPUB uses the order file to generate the program order. It checks that all papers are in the file, but if a paper is listed twice, it will generate two copies of it in the proceedings. This should be fixed.

@mjpost mjpost self-assigned this Jun 19, 2020
@rrgerber
Copy link
Collaborator

There was an ACL conference a few years ago that needed to show papers twice (I don't recall why), but in recent years that has not been the case. If there is a reason why this could happen, then we can change the program and toc generation to only point to a single paper. But if there is no need to include papers twice, we can just flag an error on it, which would be easier.

@mjpost
Copy link
Member Author

mjpost commented Jun 19, 2020

I think it's fine to list it 2+ times in the program, but it shouldn't generate two entries under cdrom/bib and cdrom/pdf, which is what I think happened (right, @bethard?)

@bethard
Copy link
Contributor

bethard commented Jun 19, 2020

Yes, ACL 2020 has every paper in two different sessions (so two different times in the schedule). EMNLP 2020 will almost certainly do the same. I would predict that this will be common as many of our conferences go virtual.

And yes, what it does now is generate two entries in cdrom and include the PDF in the full proceedings twice.

@rrgerber
Copy link
Collaborator

OK, who wants to volunteer to do this? I know the code pretty well, but don't have time until next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants