From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Tue, 09 Sep 2014 12:56:27 -0400 [thread overview]
Message-ID: <87zje8u404.fsf@yale.edu> (raw)
In-Reply-To: m21trklpl8.fsf@tsdye.com
Thomas S. Dye writes:
> 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.
Same here.
> Bibtex mode has functions for automatic reference key
> generation:
>
> http://www.jonathanleroux.org/bibtex-mode.html#0630
>
> You can configure this process.
You can also download the .bib from Google Scholar or whatever and
then clean the entry, so that your database has the same format.
> Either a separate bibtex file for each article, or separate
> bibtex files for each co-author.
Or better do both...
#+BEGIN_SRC latex
\bibliography{/home/you/references/articles.bib}
% \bibliography{/home/collaborator_1/references/articles.bib}
% \bibliography{/home/collaborator_2/references/articles.bib}
...
\bibliography{references}
#+END_SRC
When a collaborator_i is working on the file she/he comments the
first line and uncomments the i-th line AND everybody runs
reftex-create-bibtex-file (or copy paste the new references for
the unfortunate non-emacs user) after adding new references and
finishing editing. Everybody shares a current version of the .tex
file and the references.bib file.
> 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.
Note that when the article is ready the references.bib is the only
thing you need to compile, since it has all the references, so you
erase the all the other \bibliography's
> There are tools that use the information in your article .tex
> files to create this kind of bibtex file from a larger bibtex
> database.
Yes, emacs via reftex-create-bibtex-file =)
Best,
--
Jorge.
next prev parent reply other threads:[~2014-09-09 16:57 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
2014-09-09 16:56 ` Jorge A. Alfaro-Murillo [this message]
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=87zje8u404.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).