From: Christoph Groth <christoph@grothesque.org>
To: emacs-orgmode@gnu.org
Subject: Re: Managing articles in orgmode and collaboration
Date: Tue, 09 Sep 2014 11:13:46 +0200 [thread overview]
Message-ID: <87ppf5mb6a.fsf@grothesque.org> (raw)
In-Reply-To: 87k35dvnu7.fsf@grothesque.org
Hi again,
I’m replying to myself, as I think I’ve found a possible solution
to my
problem.
Most publications have some kind of unique ID that can be present
in
BibTeX: a DOI number, a ISBN, a preprint ID, or an URL. One could
use
one these fields as an org-id unique ID for the publication’s
org-mode-entry. (If several such fields are present, priorities
could
be used to choose one.) Then, org-id can be used to find article
entries by unique ID.
This way, even if a reference has been added to a project-specific
.bib-file by a collaborator (with some label of his choice), it
should
be possible to find the relevant org-mode-entry if the paper is
already
anywhere in the library. In the worst case, a missing DOI id will
have
to be added to the .bib-file-entry.
The org entry on the article would contain links and notes. The
BibTeX
data could be kept in a :BIBTEX: drawer.
Any comments?
Christoph
next prev parent reply other threads:[~2014-09-09 9:51 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ppf5mb6a.fsf@grothesque.org \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.