From: tsd@tsdye.com (Thomas S. Dye)
To: Christoph Groth <christoph@grothesque.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Tue, 09 Sep 2014 06:34:59 -1000 [thread overview]
Message-ID: <m21trklpl8.fsf@tsdye.com> (raw)
In-Reply-To: <87k35dvnu7.fsf@grothesque.org> (Christoph Groth's message of "Mon, 08 Sep 2014 22:50:24 +0200")
Aloha Christoph,
I don't manage my bibliography references in Org mode. I am used to
managing a bibtex database and have never found the need to move
everything to Org.
Christoph Groth <christoph@grothesque.org> writes:
> Most solutions seem to be based around a central BibTeX file and take
> advantage of RefTeX to navigate between citations to articles (in LaTeX
> or org files), the BibTeX file, related entries in an org-file, and
> linked external files. Often the key that connects the various items is
> a unique label (in LastnameYear format, for example). This key is used
> as label when citing and in BibTeX, as orgmode CUSTOM_ID, and as the
> filename of an associated external file.
Bibtex mode has functions for automatic reference key generation:
http://www.jonathanleroux.org/bibtex-mode.html#0630
You can configure this process.
> This seems to work well for people who have complete control over the
> articles they write. But what about articles with co-authors? These
> must be self-contained, so one needs a separate BibTeX file for each
> article project. Let’s say that a co-author adds a new reference to a
> common project, but the cited paper is already in my database under a
> different label. Maybe that very paper is already cited in an older
> article with different co-authors using a different \cite label?
Either a separate bibtex file for each article, or separate bibtex files
for each co-author. A LaTeX document can use any number of bibtex files
per document.
In general, you'll want to have the bibtex file(s) for an article only
contain the references that you'll use in the article, especially if you
intend to distribute the bibtex files as part of a reproducible research
project. There are tools that use the information in your article .tex
files to create this kind of bibtex file from a larger bibtex database.
In my work flow, I have a large legacy bibtex file with about 6,000
references. When I'm writing an article, I create another bibtex file
just for the article. I use ebib to open both the legacy bibtex file
and the article bibtex file and copy from one to the other, which ebib
makes very convenient. Then I autogenerate the reference key in ebib by
pressing 'K'.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-09-09 16:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 20:50 Managing articles in orgmode and collaboration Christoph Groth
2014-09-09 9:13 ` Christoph Groth
2014-09-09 10:48 ` Thorsten Jolitz
2014-09-09 11:40 ` Christoph Groth
2014-09-09 12:18 ` Vikas Rawal
2014-09-09 12:24 ` Fabrice Popineau
2014-09-09 12:48 ` Thorsten Jolitz
2014-09-09 14:22 ` Samuel Loury
2014-09-09 20:25 ` John Kitchin
2014-09-09 16:34 ` Thomas S. Dye [this message]
2014-09-09 16:56 ` Jorge A. Alfaro-Murillo
2014-09-09 17:30 ` Rasmus
2014-09-10 10:31 ` Christoph Groth
2014-09-10 14:33 ` Jorge A. Alfaro-Murillo
2014-09-23 13:14 ` Christoph Groth
2014-09-23 13:52 ` Jorge A. Alfaro-Murillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m21trklpl8.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=christoph@grothesque.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).