-
Notifications
You must be signed in to change notification settings - Fork 362
Ingestion: GWC #6007
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
Ingestion: GWC #6007
Conversation
|
Build successful. Some useful links:
This preview will be removed when the branch is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Papers are not lined up, e.g., https://preview.aclanthology.org/gwc-25-ingestion/2025.gwc-1.3.pdf
(You checked "Download 3–5 papers", did you not see this? I usually click over to the preview, then command-click three to five papers to open them in new tabs, then click to each's PDF to do a quick sanity check)
|
Hi, thank you for taking care of this! I wanted to ask if we could wait a while before publishing the website. The board of the Global WordNet Association mentioned the possibility of obtaining a DOI for the proceedings, and I would like to check with them if they want to talk with you about this. |
|
Yes, we can wait—the proceedings are not correct, anyway. |
|
Thank you! What shall we correct? - Sorry for this, it's the first time my colleagues and I have prepared proceedings for ACL. |
|
@mcandito The papers are not lined up. See this paper, for example, from the preview: https://preview.aclanthology.org/gwc-25-ingestion/2025.gwc-1.3/ |
|
Hi @mjpost , I think the comment is not for me?? |
|
@EricaBiagetti I double checked the material that's been submitted and the mismatch comes from the submitted material. In There's another problem with the submitted material. Could you follow instructions here to make sure the file names in Let me know once the material is updated and I can re-ingest. |
|
Thank you @mjpost! Sure, I'll let you know once the material is updated |
|
@mjpost here is the updated material: https://drive.google.com/file/d/1XfXS6iq_7LHqmFglI0CsRIaxxr-W2MPj/view |
|
Hello, we noticed some errors in the material, which my colleague Luca is fixing, so I will have to update the material again. Sorry for this! |
|
@EricaBiagetti Let us know once the material is updated. |
|
@anthology-assist Once this is ingested, please assign DOIs to all GWC volumes here and in the past. |
|
Hi, here is the updated (and hopefully final) version of the material: https://drive.google.com/file/d/1APIn71S8IyPvzHtxybMQT2JwXLKkH6J-/view?usp=sharing |
|
Hi, could I check if there is anything else that needs to be done here? I think Erica has fixed the papers and metadata, and we have SIGLEX and SIGSEM endorsement, so we should get DOIs. Francis |
|
Hi, please see the preview: https://preview.aclanthology.org/gwc-25-ingestion/volumes/2025.gwc-1/ The PDFs are still all out of sync with the metadata. |
|
In the latest zip folder we sent with the proceedings, the PDFs are correctly aligned with the corresponding BibTeX files (each |
|
Okay, this was a combination of mistakes and oversights. The volume was set as I will merge this in a few hours in a gap between meetings, and then will generate DOIs soon afterward. |
|
Hi all! Some colleagues are asking if we know exactly when the proceedings will be out, since they are preparing an application and would like to add a reference to their paper. Do we know already, or is it better if I stay vague? |
|
I just merged it now. I should be live in ~30 minutes. |
|
Thank you Matt and Erica! I can see the correctly aligned proceedings at https://aclanthology.org/events/gwc-2025/ However, they still not appear to have any DOIs, ... |
Yes, that is the next step. |
|
I have added DOIs to all GWC conferences in the Anthology. |
|
Fantastic, thank you Matt! |
(Please replace this text with a description of the changes effected by this pull request.
Include a link to the corresponding Github Issue, if there is one.
Details on how to do this (can be found here).)
masterbranch<meta>block<venue>ws</venue>tag to its meta block<event>blockAfter the PR is closed, for all events:
YYYY-MM-DD-{event}After the PR is closed, for ACL events:
generate_crossref_doi_metadata.py)add_dois.py)