-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix inconsistent bibtex key for ESEC/FSE #1
Comments
Are we sure that we would like to use only Also, retroactively renaming all such keys to use only I would argue to use I believe the initial problem was that the entries < 2024 were named inconsistently as in your example above. |
Remark: The conference was called FSE before being merged with ESEC. I am fine with either way, but consistency would be good. |
True! So its basically three conferences then. The initial FSE (which is not the same as todays FSE), ESEC/FSE, and FSE(24). 😆 |
We also potentially have such problems with other renamed conferences, and we treat each one a bit differently:
I don't know how to handle this best, but overall I like our approach with VaMoS - each paper has the correct booktitle (as of its publication date), but the keys are still pragmatic, and can be extended when a conference is renamed once more. I'm not sure how much use it is to retroactively change keys or update booktitles of old entries (e.g., for SPLC before 2005, or FSE before 2024). seems a bit perfectionistic, even for me ;) |
Fix inconsistent keys such as OBM+:FSE17 and SSA:ESECFSE17.
Only FSE should be used in keys.
The text was updated successfully, but these errors were encountered: