You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Time to agree on a standard format for keys in the proceedings :-)
In the 2020 proc, the keys have the format:
f"NIME{year}_{articleno}"
In other years, I think @alexarje has standardised to:
f"{first_author_last_name}{year}"
I don't think the key matters too much, because people often change it anyway, but should we stick a "nime" or something in there so that the default key has the conference?
e.g., it could be f"nime{year}_{first_author_last_name}"
or even f"nime{year}_{articleno}_{first_author_last_name}"
The final option there, although a bit convoluted, would make every key unique even if one author had two papers in a certain edition.
The text was updated successfully, but these errors were encountered:
I don't have a strong opinion, but I agree that it makes sense to have a unique ID across the entire collection. So I think f"nime{year}{articleno}{first_author_last_name}" makes sense. Can you write a script to fix that?
Time to agree on a standard format for keys in the proceedings :-)
In the 2020 proc, the keys have the format:
f"NIME{year}_{articleno}"
In other years, I think @alexarje has standardised to:
f"{first_author_last_name}{year}"
I don't think the key matters too much, because people often change it anyway, but should we stick a "nime" or something in there so that the default key has the conference?
e.g., it could be
f"nime{year}_{first_author_last_name}"
or even
f"nime{year}_{articleno}_{first_author_last_name}"
The final option there, although a bit convoluted, would make every key unique even if one author had two papers in a certain edition.
The text was updated successfully, but these errors were encountered: