From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Wed, 10 Sep 2014 10:33:44 -0400 [thread overview]
Message-ID: <877g1bwnnb.fsf@yale.edu> (raw)
In-Reply-To: 87ha0fzrzu.fsf@grothesque.org
Christoph Groth writes:
> My motivation for keeping bibliography in org was to keep all
> local information about a paper (including notes and comments)
> in one place. This should make it easier to find it.
In BibTeX if any field contains an entry that is not part of the
required or optional entries for the field type, that entry is
ignored. So you can do want you want in a single bib file, just
include for every field that you want a "COMMENTS" entry. The
"NOTE" entry is an optional entry for the field type article and
book, so you have to use something else, I use "ANNOTE", since it
is the standard "to be ignored" entry in the emacs BibTeX mode.
> I like to keep papers under version control, and the commenting
> that you suggest does not seem to fit this way of working very
> well.
Then change it to:
#+BEGIN_SRC latex
\include{personal_references}
\bibliography{references.bib}
#+END_SRC
And in personal_references.tex, every user has just one line:
#+BEGIN_SRC latex
\bibliography{the_user_path_to_her/his_references.bib}
#+END_SRC
Add personal_references.tex to the .gitignore file (or the
equivalent if you are not using git), and then you have version
control and no more commenting/uncommenting.
Perhaps I am biased because I learned LaTeX and BibTeX before Org,
but I think that for references BibTeX (plus a little bit of emacs
configuration) has everything I could need. I guess if you are
more used to Org, it might be worth to invest time and come up
with a org-based solution. Please keep us posted, I find this a
very interesting thread.
Cheers,
--
Jorge.
next prev parent reply other threads:[~2014-09-10 14: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
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 [this message]
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=877g1bwnnb.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).