From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Ramon Diaz-Uriarte <rdiaz02@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>, ramon.diaz@iib.uam.es
Subject: Re: more helm-bibtex/org-ref questions
Date: Fri, 26 Jun 2015 16:58:19 -0400 [thread overview]
Message-ID: <m2pp4ii3v8.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87mvzmp5uv.fsf@gmail.com>
You could have multiple file fields I suppose, and adapt [1] to give you
a choice of which one to open.
Personally, I have one pdf per bibtex entry, named by the key of the
entry, in a directory called bibtex-pdfs somewhere defined by
org-ref-pdf-directory. There are ~1300 pdfs in there now. I always
access them through helm bibtex.
admittedly, I don't have the SI or other stuff around usually. I don't
use bibtex to keep track of the directories where I write manuscripts
either.
You could always make links to these other things in the associated
notes entry. or put org-links in a bibtex field, and then you can open
them with C-c o (if you setup links to work everywhere). That way,
opening the pdf is easy, and opening the other things is just opening
the entry and running the link open command.
Ramon Diaz-Uriarte writes:
> Dear All,
>
> (I am not sure this is the appropriate place, but this is neither a bug
> report nor an feature request about helm-bibtex or org-ref, but a question
> from ignorance and I am learning quite a bit from the other helm-bibtex
> questions).
>
>
> How do people deal with multiple files that are logically associated to an
> entry?
>
>
> I've been used to keeping the main file, supplementary materials,
> associated code, etc, in a directory per entry. This kind of modus operandi
> is something I adopted (fell into?) easily with Zotero and Mendeley. But I
> am not sure that this is the best way to proceed.
>
>
> If I end up with multiple files per directory, helm-bibtex-find-pdf[1]
> cannot know which one I want to open. I could keep the main file in the
> general directory, so it is found directly by helm-bibtex-find-pdf and
> specify other files (of secondary usage) in the "file" field (and maybe
> open them via ebib when/if needed)? But this does not seem
> elegant. Another is to have an entry per file, with unique key, but this
> does not seem right.
>
>
>
> Thanks,
>
> R.
>
>
> [1] Thanks to Titus' help
> (https://github.com/tmalsburg/helm-bibtex/issues/53), opening a PDF that is
> given in the "file" field with the directory name is now within my reach.
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-06-26 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 20:33 more helm-bibtex/org-ref questions Ramon Diaz-Uriarte
2015-06-26 20:58 ` John Kitchin [this message]
2015-06-27 10:15 ` Ramon Diaz-Uriarte
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=m2pp4ii3v8.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=ramon.diaz@iib.uam.es \
--cc=rdiaz02@gmail.com \
/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).