Skip to main content

Handling Publications, Preprints, and Talks in the BibTeX Bibliography

The file local.bib stores all our publications. To handle it, you must follow some general rules when adding your BibTeX file. First, please use regular article types, do not use fancy types like @inbook, only incollection, article, book or phdthesis, we usually do not have many more.

Each BibTex entry has a couple of extra fields that must be submitted. These are:

  • sortauthor: needed to determine the order in which articles appear on the website,
  • _doi: to display the DOI prominently on the website,
  • `_pdf': a direct link to the PDF if you wish to include it (usually, the DOI is enough),
  • _draft: a URL linking to the draft (can also be a DOI),
  • keywords: to determine the project in which the research was carried out and to provide three (only three) keywords.

Field sortauthor in local.bib

A field that makes sure the order on the website is handled well (only not required for talks, where we have clear dates). To find out what to put here, please go to the website and check in which section your paper will appear (preprint, forthcoming, or the current year). Then go to the top-most article in the section and check the formula. E.g. in the year 2024, we have the article by Kim and Tjuka (2024).

Kim, Y. and A. Tjuka (2024): Cognitive science from the perspective of linguistic diversity. Cognitive Science 48.2. 1-5.

The BibTeX entry looks as follows:

@Article{Kim2024,
  author      = {Kim, Yoolim and Tjuka, Annika},
  title       = {Cognitive science from the perspective of linguistic diversity},
  number      = {2},
  pages       = {1-5},
  volume      = {48},
  _doi        = {10.1111/cogs.13418},
  sortauthor  = {Papers, 3}, 

  journal     = {Cognitive Science},
  keywords    = {_calc3, cognitive science, linguistic diversity, concepts},
  publisher   = {Wiley},
  year        = {2024},
}

The sortauthor field shows Papers, 3 as value, so any new paper in 2024, should be Papers, 4. From Papers, 9 on, we would start to use Papers, A, Papers, B, etc.

Field keywords in local.bib

The field is comma-separated (we use comma plus space) and contains maximally three keywords, plus specific keywords referring to the project in which the study was published. Thus, _produsemy refers to the ProduSemy project, _calc3 to the CALC³ project, and _mcl to projects only published by the chair, not identified with any project.

Specific Format for Preprints

For preprints, we use a custom BibTeX class called @Preprint, which is rendered in a specific form. When using it, you can fill it in like an article, but volume and number and pages should be filled in by using the year for the volume, the month (numerical) for the number, and the pages starting from one to the number of pages as in teh PDF submitted to the preprint server. The journal is the preprint server. An example is given below.

@Preprint{List2024PREPRINTa,
  author     = {List, Johann-Mattis},
  journal    = {Humanities Commons},
  number     = {0},
  title      = {Productive Signs: A computer-assisted analysis of evolutionary, typological, and cognitive dimensions of word families},
  volume     = {0},
  year       = {2024},
  _doi       = {https://doi.org/10.17613/zfwr-sn25},
  _pdf       = {https://hcommons.org/deposits/download/hc:63328/CONTENT/list-2024-productive-signs-preprint.pdf/},
  groups     = {Preprints},
  keywords   = {_produsemy, word families, lexical compositionality, computer-assisted language comparison},
  pages      = {1-12},
  sortauthor = {Preprint, 6},
}

Specific Format for Talks

For talks, we have the BibTeX type @customa, and we have some specific fields that must be submitted. Consider the example below.

@Customa{Forkel2024TALKa,
  author       = {Forkel, Robert and List, Johann-Mattis},
  eventdate    = {2024-02-26/2024-03-30},
  eventtitle   = {Digital Humanities im deutschsprachigen Raum},
  howpublished = {talkconference},
  title        = {Cross-Linguistic Data Formats (CLDF): D’où Venons Nous? Que Sommes Nous? Où Allons Nous?},
  venue        = {Passau},
  year         = {2024},
  organization = {University of Passau},
  groups       = {Talks},
  keywords     = {_mcl, cross-linguistic data formats, CLDF, overview},
}

Here, you can see that we have the event-date (which is from to, minimally, you must submit one day). You must provide the title of the event, the venue, and the entry howpublished is a shortcut that we resolve automatically.

Thus, talkconference is resolved as follows on the website:

Forkel, R. and J.-M. List (2024): Cross-Linguistic Data Formats (CLDF): D’où Venons Nous? Que Sommes Nous? Où Allons Nous?. Talk, held at the conference "Digital Humanities im deutschsprachigen Raum" (2024/02/26-03/30, Passau, University of Passau).

To make sure you use the correct short cut, please compare with similar entries (e.g., if it is no conference, but a workshop). The individual short cuts are as follows:

self._modifiers = {
    'paperconference' : 'Paper, presented at the conference',
    'paperworkshop': 'Paper, presented at the workshop',
    'talkconference': 'Talk, held at the conference',
    'talkworkshop': 'Talk, held at the workshop',
    "keynoteat": "Keynote, held at the conference",
    "lectureseries": "Talk, given for the lecture series",
    'talkatm': 'Talk, held at the'
    }
Back to top