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

CLT workshop at COLING 2025 #4600

Closed
ThFransen84 opened this issue Feb 10, 2025 · 7 comments · Fixed by #4558
Closed

CLT workshop at COLING 2025 #4600

ThFransen84 opened this issue Feb 10, 2025 · 7 comments · Fixed by #4558
Assignees

Comments

@ThFransen84
Copy link

ThFransen84 commented Feb 10, 2025

The preview doesn't show changes to CLT at https://preview.aclanthology.org/ingest-more-coling/volumes/2025.cltw-1/.
In case it's possible, could you redo with zip file below? This is also because there seems to be a lot of inconsistency with titlepage and copyright pages across workshops; have slightly updated this today but can still redo based on your requirements.

proceedings_cltw.zip

A less desirable option is to only redo the following, most pressing issues, more or less reflecting updates by emilyallaway at #4557 (comment) (in terms of the pdf(s), this doesn't affect the page number sequence in any of the versions so far)

As far as I can see, in terms of the pdfs, either option results in the replacement of 3 pdfs anyway:

  • the "pre-scientific" pre-amble part up until and including the schedule (2025.cltw-1.0.pdf)
  • paper 1.4
  • the entire book

Sorry for the long message and potential lack of clarity due to being unfamiliar with your workflow and the associated GitHub threads.

          <!-- add-pr-comment:preview -->

Build successful. Some useful links:

This preview will be removed when the branch is merged.

Originally posted by @github-actions[bot] in #4558 (comment)

@mbollmann mbollmann changed the title <!-- add-pr-comment:preview --> CLT workshop at COLING 2025 Feb 10, 2025
@ThFransen84
Copy link
Author

ThFransen84 commented Feb 10, 2025

Just a clarification: with either option each paper pdf would need to be redone as the footer stamp (only) has been updated, too (even though the page numbering has remained the same so far).

@mjpost
Copy link
Member

mjpost commented Feb 12, 2025

Hi, we cannot receive this volume because you changed the paper order, which changes Anthology IDs (e.g., https://aclanthology.org/2025.cltw-1.1/). Once published, these cannot change. If you want to add papers, you need to add them to the end and regenerate the proceedings.

@mjpost
Copy link
Member

mjpost commented Feb 12, 2025

My mistake—I was looking at the wrong volume. These have been added to #4558. I'm waiting for two other updated volumes and can then merge.

mjpost added a commit that referenced this issue Feb 12, 2025
@ThFransen84
Copy link
Author

Thanks very much! There is one minor slip left: the surname part "Ui" in one of the editors' name should be "Uí". I think this was corrected everywhere including in the metadata so it seems to be an artefact from the previous version (it's fine in the PDFs - so maybe I can just do a "fix data" request?). N.B. This slip arose from funny text encoding/display in START, which doesn't properly render accented characters.

@mjpost
Copy link
Member

mjpost commented Feb 12, 2025

This has been corrected and is visible in the preview: https://preview.aclanthology.org/ingest-more-coling/volumes/2025.cltw-1/

When we merge the PR, it will be live.

If you want a quicker correction on just that, you can create a PR with an edit.

@mjpost
Copy link
Member

mjpost commented Feb 12, 2025

(Fix data would work, those are processed weekly, so likely this Friday).

@ThFransen84
Copy link
Author

I think I'll be patient and wait. :-) Many thanks again.

@mjpost mjpost linked a pull request Feb 13, 2025 that will close this issue
12 tasks
@mjpost mjpost closed this as completed in db5625e Feb 13, 2025
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

Successfully merging a pull request may close this issue.

2 participants