I am using revtex4-2, with no particular bibliography style. But, I see that some of the references get listed with incomplete details. For instance, a bibtex entry

    title={Repeated averaging and bounded confidence-modeling, analysis and simulation of continuous opinion dynamics},
    author={Lorenz, Von Jan},

appears as enter image description here

  title={Consensus formation on adaptive networks},
  author={Kozma, Balazs and Barrat, Alain},
  journal=Phys. Rev. E},

appears as enter image description here

I have tried using \bibliographystyle{apsrev4-2}, but that doesn't fix the issue.

  • 2
    There is a syntax error in kozma2008consensus: journal=Phys. Rev. E}, is missing an opening brace, it should be journal={Phys. Rev. E},. An error like this can mean that BibTeX has to abandon any attempt to parse the entry and may lead to incomplete data.
    – moewe
    Mar 15 '20 at 6:47
  • 2
    Re the first entry: A short google search suggests the entry is not actually a journal @article (rule of thumb: It's only an @article if you can give a journal.), it appears to be a PhD thesis, in which case @phdthesis or @thesis is more appropriate. @articles never show the publisher field and your style does not appear to print @article titles, so that's what you get. You may also want to double check the name author={Lorenz, Von Jan},. As far as I can see the author is called author={Lorenz, Jan},. The "von" on the title page is German for "by".
    – moewe
    Mar 15 '20 at 6:50
  • 1
    It is always wise to double check .bib entries you obtain from tools such as Google Scholar. Sometimes the entries those tools export are of extremely low quality, sometimes even wrong. See the extensive list of problems with such entries at tex.stackexchange.com/q/386053/35864 (and there are more problems ...).
    – moewe
    Mar 15 '20 at 6:58
  • 1
    I added the example lorenz2007repeated to tex.stackexchange.com/a/386054/35864. As it turns out the title field is also wrong.
    – moewe
    Mar 15 '20 at 7:22
  • 1
    @user206089 - Relying on the complete correctness of the bibliographic output produced by Google Scholar, other online search engines, and (yes!) even the publishers' own websites is -- sad but true -- rarely justified. Getting the entry type wrong and butchering one more names of authors and editors are among the more common mistakes. In addition, syntax errors such as (i) missing opening and closing curly braces to denote the argument of a bibliographic field and (ii) lack of a comma to denote the end of a bibliographic field, are unfortunately not all that uncommon.
    – Mico
    Mar 15 '20 at 9:08


The entry lorenz2007repeated is not an @article. A short Google search reveals that it is a PhD thesis.

  author = {Jan Lorenz},
  title  = {Repeated Averaging and Bounded Confidence:
            Modeling, Analysis and Simulation of Continuous Opinion Dynamics},
  school = {Universität Bremen},
  year   = {2007},

Note the corrected author field (the author is called Jan Lorenz not "von Jan Lorenz"), the corrected title field ("confidence-modeling" seems to be a botched attempt to mark up the subtitle) and finally the corrected entry type @phdthesis.

The rule of thumb is: If the entry doesn't have a journal, it is not an @article.

Since Google Scholar did a particularly bad job at this entry, I added it to the list of horrors at Software-generated bibliographic entries: common errors and other mistakes to check before use.


The entry kozma2008consensus is simply missing an opening brace in journal=Phys. Rev. E},. That syntax error means that BibTeX has to give up reading the entry at that point.

  title     = {Consensus formation on adaptive networks},
  author    = {Kozma, Balazs and Barrat, Alain},
  journal   = {Phys. Rev. E},
  volume    = {77},
  number    = {1},
  pages     = {016102},
  year      = {2008},
  publisher = {APS}
  • +1 for adding this example to the "list of horrors" posting. :-)
    – Mico
    Mar 15 '20 at 9:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.