My work involves producing various documents with citations (e.g., journal articles, conference presentations, reports, etc.).
Publications cite references, and references can be specific to a given publication, or to a set of publications built around a study, or a set of studies, or a research program. A reference may even cross-over into multiple research programs.
I'm a big fan of the DRY Principle (i.e., Don't Repeat Yourself).
However, I'm also a big fan of making projects portable.
Satisfying both principles seemingly leads to a conflict in relation to bibtex files.
- Is it a good strategy to have a single master bibtex file for all projects and adopt some automated copying system whereby each publication gets a copy of the overall bibtex file (or a subset)?
- Or is it better just to have lots of little publication specific bibtex files?
- Or is there some other system that people find works best?
- What tools can assist?
Best Answer
I just keep everything in one big BibTeX database and use the search function in JabRef.
If I really need to give away a subset of the references to a co-worker (and don't want to send the whole file), I generate a new, smaller .bib-File using the "New subdatabase based on AUX file" from the Tools menu in JabRef.
But ultimately, you'll just adopt a system that works best for you. Mendeley has been suggested, I've also heard good things about CiteUlike.