Basically a white paper is a technical report. At www.cse.msu.edu you will find this example:
@TECHREPORT{MSU-CSE-06-2,
AUTHOR = {R. Behrends and L. K. Dillon and S. D. Fleming and
R. E. K. Stirewalt},
TITLE = {White paper: Programming according to the fences and gates
model for developing assured, secure software
systems},
NUMBER = {MSU-CSE-06-2},
INSTITUTION = {Department of Computer Science, Michigan State University},
ADDRESS = {East Lansing, Michigan},
ABSTRACT = {This white paper describes extensions to our work on the
Synchronization Units Model (Szumo) to address the
access-control problem in systems assembled dynamically from
trusted and untrusted components. Our extension employs
explicitly declared design contracts, the semantics of which
are founded on Landwehr's model of fences and gates.
},
KEYWORDS = {access control, security, contracts, Szumo},
NOTE = {},
MONTH = {January},
YEAR = {2006},
AUTHOR1_URL = {http://www.poker-ping.info},
AUTHOR1_EMAIL = {kel@wondering-jons.com},
AUTHOR1_URL = {},
AUTHOR1_EMAIL = {behrends@cse.msu.edu},
AUTHOR2_URL = {Sle},
AUTHOR2_EMAIL = {Poker Ping},
AUTHOR2_URL = {http://www.cse.msu.edu/~stire},
AUTHOR2_EMAIL = {stire@cse.msu.edu},
PAGES = {3},
FILE = {/user/web/htdocs/publications/tech/TR/MSU-CSE-06-2.ps},
URL = {},
CONTACT = {stire@cse.msu.edu}
}
Indeed, there's a plethora of bibliography style files (extension .bst), but no central repository that lists what each of them does. The four "classic" .bst files -- thus-named because they came with the initial release of BibTeX -- are "plain.bst", "unsrt.bst", "alpha.bst", and "abbrv.bst"; see the BibTeX manual for information on these styles.
The "classic" style files were designed originally for numeric citation methods, but citation management packages such as harvard and natbib were developed that let you use these style files with author-year citation methods. The natbib
package comes with abbrvnat.bst
, unsrtnat.bst
, and plainnat.bst
, all of which recognize more fields -- including, you guessed it, the "url" field -- than the classic style files do.
The "classic" bst files recognize the following fields for an entry (of course, not all fields make sense for all entries):
address, author, booktitle, chapter, edition, editor,
howpublished, institution, journal, key, month, note,
number, organization, pages, publisher, school,
series, title, type, volume, year
The natbib bst files, in addition, recognize (i.e., "know what to do with") the following five fields:
doi, eid, isbn, issn, url
Assuming that quite a few of your entries will have url and doi fields, I recommend you go for one of the newer bst files rather than stick with the classic ones.
A big plus of the natbib
package (which lets you do both numeric and auhor-year type citations, by the way) is that it works very well with the hyperref
package. If hyperref
is a package you're contemplating using, but if you're already using harvard
and don't want to re-write all citation commands just to conform to the natbib syntax, don't despair: From now on, just load both the natbib
and har2nat
packages (and don't load the harvard
package anymore). The har2nat
package, you guessed it, translates the "harvard"-style citation commands into "natbib"-style citation commands...
Best Answer
For forthcoming articles of the sort that you give in your question, the easiest solution is to simply format them as
article
type, and then put "to appear" in thepages
field. A forthcoming article won't have a page range yet, and when the article is published you will have to add the page range anyway. In theecon
bibliography style, (and in fact most bibliography styles forarticle
) the page range appears last in the entry, so it will be formatted as you wish.Alternatively, (as pointed out in the comments) you can add the "to appear" as a
note
field. To do this in BibDesk, you need to do the following:This solution is semantically good, but in practice it may not be as robust as putting the "to appear" in the
pages
field, since the appearance of the field depends on the particular bibliography style you are using; if the style isn't set up to output thenote
field, then the problem will reappear.(Another common way to do this is to not give a year, and replace the
year
field with "to appear". This will, of course, replace it in both bibliography and citations.)For chapters in books, the
incollection
entry type should be used. Theinbook
entry (which may have been what you were using) is really designed for referring to a particular chapter of a single-authored or edited book; you're not likely to use it much at all, since most citations of that sort can be done using thebook
entry and adding the chapter reference to the citation command.