When exporting using BBT you will be offered a new export option:
Keep updated. Checking this option
registers the export for automation; any changes to the collection or library you exported after you’ve completed the current export will
trigger an automatic re-export to update the bib file. You can review/remove exports from the BBT preferences. While
I’ve gone to some lengths to make sure performance is OK, don’t go overboard with the number of auto-exports you have
going. Also, exporting only targeted selections over your whole library will get you better performance. You can set up
separate exports for separate papers for example if you have set up a collection for each.
After you’ve set up an auto-export using an
Keep updated export,
you can manage your auto-exports in the BBT preferences under the
Automatic exports tab. There, you can remove auto-export, change
settings on them, or remove them. You cannot add new auto-exports
from here, that can only be done by initiating an export.
You may want to use your BBT generated bib(la)tex on other systems; maybe you use Overleaf (as I do), maybe you have your documents compiled using Travis (as I do). In any case, you want your auto-exported items to show up somewhere else. If you’re thinking of this in the context of Overleaf, here’s a TL;DR of the pros and cons:
Or any other of the plethora of choices that are available today that will “cloud-sync” your files. Just auto-export your bib file to a cloud-synced folder, and Bob’s your uncle. Incidentally, this should work with Overleaf, but I have not tested it personally, as I use…
BBT auto-export works nicely with git services (such as Overleaf, which is where I use it myself; the instructions for setting up Overleaf for git can be found here – note these instructions are for Overleaf V1 projects, not V2 projects, which will get git support only late 2018), but any git service (gitlab, github, etc) should work exactly the same. I’m toying with various online services here.
Note that this is more for the technically inclined, you will need to be comfortable with the command line to set this up. I can’t think of a real benefit to using git over cloud-sync unless, like me, you like to keep a backup history in git.
To activate git support, first clone the repo that holds your article/thesis/whatnot from your provider (github, overleaf, etc), run
git config zotero.betterbibtex.push true in a command shell in that clone, and set up an auto export to that directory; at each update, BBT will now also push your library to the git service. For the technically curious, that means it does:
git add <your library file>
git commit -m <your library file>
Note that the nature of git commit/push is not file-bound; if you made edits to other files, and added those, they will be committed and pushed along. If you want to be super-careful, the best way to go about it is to have a separate clone of your repo that BBT auto-exports to, and then another repo that you do your own edits in. I don’t use it myself this way, but you have been warned.
If you only want BBTs citation keys on Overleaf, you can simply pin them and use the regular Overleaf-Zotero integration. This will get you the pinned keys, but the bibtex is generated by the standard Zotero exporters.