An example from biblatex-examples.bib
:
@inproceedings{salam,
author = {Salam, Abdus},
editor = {Svartholm, Nils},
title = {Weak and Electromagnetic Interactions},
date = {1968},
booktitle = {Elementary particle theory},
booksubtitle = {Relativistic groups and analyticity},
booktitleaddon= {Proceedings of the Eighth Nobel Symposium},
eventdate = {1968-05-19/1968-05-25},
venue = {Aspen{\"a}sgarden, Lerum},
publisher = {Almquist \& Wiksell},
location = {Stockholm},
pages = {367-377},
}
So if there is a dedicated title field, standard seems to be to put the "Proceedings of ..." part into the (book)titleaddon
field.
It is probably best to put 2013 28th Annual ACM/IEEE Symposium on Logic in Computer Science
into the title
field, if there is no other title available - after all we do not want to have an empty title
field.
@proceedings{lics,
title = {2013 28th Annual ACM/IEEE Symposium on Logic in Computer Science},
shorttitle = {LICS},
eventdate = {2013-06-25/2013-06-28},
venue = {New Orleans, Louisiana},
isbn = {978-1-4799-0413-6},
publisher = {IEEE Computer Society},
date = {2013},
}
@inproceedings{pattinson,
author = {Pattinson, Dirk},
title = {The Logic of Exact Covers},
subtitle = {Completeness and Uniform Interpolation},
crossref = {lics},
pages = {418-427},
}
Another solution would be your third idea, though that does not reflect the title information as given in the proceedings itself.
@proceedings{lics,
booktitle = {Logic in Computer Science},
booktitleaddon = {Proceedings of the 28th Annual ACM/IEEE Symposium},
shorttitle = {LICS},
eventdate = {2013-06-25/2013-06-28},
venue = {New Orleans, Louisiana},
isbn = {978-1-4799-0413-6},
publisher = {IEEE Computer Society},
date = {2013},
}
Since the question is tagged as biblatex, I answer with some quotes from the biblatex
documentation (which you can get from here).
Regular Types
proceedings
A single-volume conference proceedings. This type is very similar to @collection
.
It supports an optional organization
field which holds the sponsoring institution.
The editor
is omissible in terms of ยง 2.3.2.
Required fields: title
, year
/date
inproceedings
An article in a conference proceedings. This type is similar to @incollection
. It
supports an optional organization
field.
Required fields: author
, title
, booktitle
, year
/date
Type Aliases
conference
A legacy alias for @inproceedings
.
To summarize:
proceedings
is intended for a collection of articles, typically the written-up contributions of one conference. You use proceedings
when you want to refer to the collection at large, and not to a single article. A proceedings
reference thus typically has an editor
specified rather than an author
.
inproceedings
on the other hand refers to a single article or contribution within a collection, i.e. typically a single written-up conference talk. You use it to refer to this specific contribution, and thus typically specifiy an author
.
conference
is only kept for compatibility reasons, use inproceedings
instead.
Best Answer
I have done the following (ok, this is just a simplified version of it...):
I have a "database" that contains the details of the conferences in a machine-readable form. It contains information like the abbreviation, the full name of the conference, an almost-full name (with some irrelevant things like "Annual International" removed), location, month, year, publisher of the proceedings, and details such as LNCS volume number if the book was published in Springer's LNCS series.
Then I have a Python script that reads the database and outputs several Bibtex files: long.bib, medium.bib, short.bib. These contain Bibtex entries for conference proceedings, with different amounts of details. For example, long.bib might contain details like
while short.bib might contain just
Once again, all this is machine-generated.
In my Bibtex database (articles.bib) I have crossreferences to conference proceedings. All details come from long.bib/medium.bib/short.bib.
I can easily change the amount of detail by choosing one of the following in any paper that I am writing:
And if I ever wanted to switch from "Proc. ..." to "Proceedings of ...", I only need to change it in one place.
Of course I'll have to run
bibtex -min-crossrefs=999
so that I don't have any crossreferences in the Bibtex output...Works fine until you have to explain all this to your coauthors. :)
By the way, you can use
bib2bib
from the bibtex2html package to "flatten" the bibliography. Then you will have just one Bibtex file, less confusion with coauthors, no crossreferences, and no need to specify-min-crossrefs
. I have a script that does something along these lines: