Online resources like this:

  author = {Google},
  year = {2012},
  month = "April",
  title = {Google App Engine Datastore Java API},
  url = "https://developers.google.com/appengine/docs/java/datastore/",
  note = "[Accessed: June 2012]"

have an "all lowercase" title in my bibliography. Non-@MISC resources display just fine.

Example: (the above is displayed as follows)

Google (2012), `Google app engine datastore java api'. [Accessed: June 2012]. URL: https://developers.google.com/appengine/docs/java/datastore/

I am using:


and quoting without citation:


Any ideas as to why?

Also, could I have the [Accessed: Month Year] block appear after the nicely formatted URL?

  • 1
    It is the standard way BibTeX works. If you want uppercase letters in the title just write: title = {{G}oogle {A}pp {E}ngine {D}atastore {J}ava {API}}. To change the appearance of the accessed block you need to change the style of bibliography.
    – Mensch
    Jul 22, 2012 at 21:40

1 Answer 1


You pose two questions. First, to keep the words in the title field -- other than the first one, viz., "Google" -- from becoming set in all-lowercase, encase the publication's title in a second pair of curly braces. I.e., set up the field as

title = {{Google App Engine Datastore Java API}},

The second question is about how to change the ordering of the output of the fields url and note, given that you're using the agsm bibliography style. The problem with this request is that the ordering of fields of various entry types (article, book, techreport, ...) is currently consistent across all of these entry types in the agsm style. It might look downright weird to your readers if the ordering were changed for some entry types only. I would therefore advise against fiddling with the ordering of the fields in the function misc of the file agsm.bst. If you do decide to edit that file, be sure to save it under a new name (say, myagsm.bst) rather than overwriting the existing file.

  • Answer 1) -> GOLDEN PERFECTION. You are awesome, man. I am becoming a fan. Answer 2) -> Alright, the problem with "plainnat" is that urls look really ugly in it. Do you have a better .bst to use with 'natbib'? Jul 22, 2012 at 21:45
  • 2
    @Robottinosino -- I'm blushing... About the bibliography style: I thought you were using agsm, but now you're suggesting that it's plainnat. May I suggest that you post a new question to this group, in which you describe in detail how you would like to see the URLs typeset? (Labeling an existing URL typesetting style "really ugly" does not provide much to go on...)
    – Mico
    Jul 22, 2012 at 23:03
  • Sure, I will post another question. I am using agsm, I was only saying "I am using agsm because I dislike URL handling in plainnat".. Jul 22, 2012 at 23:50
  • Hint for Citavi users: Citavi offers an option when exporting to bibtex to add the double-curly-braces.
    – vatbub
    Jan 28, 2021 at 17:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .