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.

Sign up for GitHub

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

Jump to bottom

guidance for mismatching year #170

Open
siccegge opened this issue Sep 2, 2022 · 4 comments
Open

guidance for mismatching year #170

siccegge opened this issue Sep 2, 2022 · 4 comments

Comments

@siccegge
Copy link
Contributor

siccegge commented Sep 2, 2022

Hi!

was trying to import FOCS21 but this conference curiously (well, ...) happend in 2022 (but there's also going to be FOCS22 of course)

is there a good way to map this in the cryptobib system?
@thomwiggers
Copy link
Contributor

Relatedly, there's proceedings like CRYPTO '93, where the date in year reflects when the proceedings came out (1994), but the month and dates reflect when the conference took place...

Another one of these is Latincrypt 2017 (LC17), of which the proceedings came out in 2019. Here, the month field also reflects the conference.

@thomwiggers thomwiggers mentioned this issue Sep 12, 2022
Merged
@siccegge
Copy link
Contributor Author

ah perfect, thanks for the pointers!

@thomwiggers
Copy link
Contributor

I found this entry in the dblp FAQ: https://dblp.org/faq/16154785.html

@thomwiggers
Copy link
Contributor

Asiacrypt 2022 is another one of these cases #197

@thomwiggers thomwiggers mentioned this issue Oct 3, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@siccegge @thomwiggers