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

Fix inconsistent bibtex key for ESEC/FSE #1

Open
skrieter opened this issue Mar 4, 2025 · 4 comments
Open

Fix inconsistent bibtex key for ESEC/FSE #1

skrieter opened this issue Mar 4, 2025 · 4 comments

Comments

@skrieter
Copy link
Contributor

skrieter commented Mar 4, 2025

Fix inconsistent keys such as OBM+:FSE17 and SSA:ESECFSE17.

Only FSE should be used in keys.

@pmbittner
Copy link
Contributor

Are we sure that we would like to use only FSE in keys? After all, the conference used to be called ESEC/FSE in the past, so the old keys should probably be still called SSA:ESECFSE17?

Also, retroactively renaming all such keys to use only FSE would introduce an inconsistency to our key naming rules, specific to FSE. Usually, the venue name in the key should be equal to the variable we use in booktitle. Here it would be different though because the key would always be <authors>:FSE<year> even when we have to use the ESECFSE variable for entries from 2023 and earlier.

I would argue to use FSE for every entry >= 2024, and ESECFSE for any prior entries.

I believe the initial problem was that the entries < 2024 were named inconsistently as in your example above.

@tthuem
Copy link

tthuem commented Mar 4, 2025

Remark: The conference was called FSE before being merged with ESEC.

I am fine with either way, but consistency would be good.

@pmbittner
Copy link
Contributor

True! So its basically three conferences then. The initial FSE (which is not the same as todays FSE), ESEC/FSE, and FSE(24). 😆

@ekuiter
Copy link
Member

ekuiter commented Mar 5, 2025

Usually, the venue name in the key should be equal to the variable we use in booktitle.

We also potentially have such problems with other renamed conferences, and we treat each one a bit differently:

  • the key VaMoS has booktitles VaMoS and VaMoS20 - still, the key is always VaMoS.
  • the SPLC conference was merged from SPLC+PFE, and technically also renamed several times (Software Product Line Conference -> International Software Product Line Conference -> International Systems and Software Product Line Conference) - we only use the latest name in bibtags.

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 ;)

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

4 participants