According to my bibtex files, I have made citations in my various published articles to 71 different posts on MathOverflow, both questions and answers, often multiple times in different articles, when the topic recurs in follow-up articles, such as in the emerging literature on infinite chess. I cite MathOverflow whenever it is relevant, and this has been the case in numerous circumstances.
I am truly thankful that it is easy and convenient to cite MathOverflow questions and answers. One need only click the "cite" button to get usable bibtex code for that post.
However, the default bibtex code that is provided can be improved in several respects. The current format seems to be a hodgepodge of sorts implementing various compromises, but I think we can design a more robust default bibtex format.
Let me explain what I would like to see. Currently, for example, if I click on "cite" on my post answering Extensions of PA+$\neg$Con(PA) with large consistency strength, what I get is:
@MISC {457828,
TITLE = {Extensions of $PA+\neg Con(PA)$ with large consistency strength},
AUTHOR = {Joel David Hamkins (https://mathoverflow.net/users/1946/joel-david-hamkins)},
HOWPUBLISHED = {MathOverflow},
NOTE = {URL:https://mathoverflow.net/q/457828 (version: 2023-11-06)},
EPRINT = {https://mathoverflow.net/q/457828},
URL = {https://mathoverflow.net/q/457828}
}
What I would like to get is something more like this:
@MISC {MO457828,
TITLE = {Extensions of $PA+\neg Con(PA)$ with large consistency strength},
AUTHOR = {Joel David Hamkins},
authorid = {1946},
authorurl = {https://mathoverflow.net/users/1946/joel-david-hamkins},
HOWPUBLISHED = {MathOverflow answer},
year = {2023},
keywords = {lo.logic},
URL = {https://mathoverflow.net/q/457828},
urldate = {2023-11-06}
}
[Note: I updated the date format to YYYY-MM-DD per Willie's answer.]
To explain the requested features:
- The year field should be set to the year of the post. This is an important basic bibtex field, which should definitely be set, but is not set in the default behavior.
- The howpublished field should differentiate between "MathOverflow question" and "MathOverflow answer". This is an important distinction that I always observe in my own citations, and I think it should become standard.
- The bibentry id can be improved by prefacing MO to the id number. This would follow MR practice. I expect that most people will make further edits to the id to follow their own personal naming practice.
- The keywords fields can be set to a comma-separated list of the tags on the main post. This field is used currently by many bibtex styles, as well as by various web apps, mainly for the purpose of sorting bibliographies by topic.
- The url should be in the url field only. Why are we setting the url in three different fields? When I use the bib data as-is, the url shows up three times in my bibliography. This weird handling of the url seems to have arisen as a compromise trying to accommodate various outdated bibtex usage practices (some predating the common use of urls), but is incompatible with current best practice. I think we should instead settle upon a robust sensible bibtex format, which will work going forward with current and new bibtex formats that people might design. Specifically, for the treatment of urls, I believe the most sensible format will be to use the url and the urldate fields.
- the urldate should be set to the date of the post (or the date of access?). This is exactly what this field is for.
- The author field should be used for the author name only, that is, the username. The other author information such as the id number and the url can be placed into other sensible author fields as I indicate. This will allow for easy edits of the bibtex entry, if someone should want to place that information into the author field, such as in the case of an anonymous author, but will also work well for what in my experience has been the main use case, where one is citing an author by their actual name. The authorurl field will enable bibstyles easily to set the author name itself as a hyperlink.
Question. What other requested behavior of the cite function might there be?