-
Notifications
You must be signed in to change notification settings - Fork 292
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 Request: JLCL #3933
Comments
@wartaal Could you share the ingestion material here? |
Yes, of course. I apologize for the delay. |
Hi, why are there two volumes, the second with just two papers? They both have the same volume name. The names should be different. |
Good morning, in 2023 we published 2 issues of the journal: a regular issue and a special issue on song texts. My idea was to ingest each JLCL issue as a separate volume in the anthology. The volumes are called "Journal for Language Technology and Computational Linguistics, Vol.36. No. 1" and "... No. 2. (Or ist there a copy and paste error at some point?) Indeed, we had only two publications in the regular issue. If you think it is better to put all papers of all issues of one year into one ACL-Anthology volume, that would of course not be a problem to do so. |
@mjpost I think the identical volume names arise because the venue is not properly marked as a journal in the metadata. The bibliographic info on the preview is for a conference proceedings. |
I think the bib-files are quite clear, but the problem is in the meta-files. Is that correct? How should the meta-file look like? I found only examples of this file for conference proceedings. What fields neend to be present for a journal? |
Multiple volumes is fine; the issue as I see it is that they are indistinguishable by name: https://preview.aclanthology.org/jlcl-ingestion/venues/jlcl/ For example, for other journals, the issue information is added to the booktitle: https://aclanthology.org/venues/cl/ Do you not want to do something similar? |
Yes! That is exactly what I would like to be it. What I put in the meta file is abbrev JLCL I guess the shortbooktitle is the problem and I should make that identical to the booktiltle? |
Hmm, if that's what you had, then it seems we mis-parsed it. I just made the edit. If the new preview (should be live within half an hour) checks out, let me know, and I can merge this. |
Thanks a lot! The preview looks good for me! |
Is there anything I should do to complete the ingestion of JLCL Volume 36? When will the volume become visible in the anthology? |
Hi, it's been live for some time! https://aclanthology.org/venues/jlcl/ Or did you mean you want it linked from the front page? We could do that, we just don't typically do it by default. |
Hi, sorry, I didn't notice that. Yes, it would be great, if you could link it from the front page. |
General information about this request
Venue Identifier
JLCL
ACL SIG(s) sponsoring or endorsing the whole venue
No response
Volume Title
Volume 36
Venue Name (only if you are submitting a new venue)
Journal for Language Technology and Computational Linguistics
Venue Website (only if you are submitting a new venue)
https://jlcl.org/
Date of Publication
No response
Location
No response
Supporting Information
JLCL is a journal, noty a conference. I would start ingesting Volume 36 (2023) and once that works fine, do the same for some previous volumes.
We had already contact on this topic over e-mail.
The text was updated successfully, but these errors were encountered: