From: Matt Lundin <mdl@imapmail.org>
To: Rasmus <rasmus.pank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: zotero (or mendeley) integration with org
Date: Tue, 29 Mar 2011 09:14:16 -0400 [thread overview]
Message-ID: <8739m6oyqf.fsf@fastmail.fm> (raw)
In-Reply-To: <imsdop$on2$1@dough.gmane.org> (Rasmus's message of "Tue, 29 Mar 2011 12:55:10 +0200")
Rasmus <rasmus.pank@gmail.com> writes:
>> [Matt and William's setup]
>
> I have looked for a good way to keep track of academic papers (pdfs) and
> Bibtex for a long time. I'd love to see a worg page on this topic.
>
> Meanwhile, I have found some sweet Bibtex-search interfaces for
> Emacs. These will query a academic search engine and can copy Bibtex
> entries directly to a .bib file. I found bibsnarfl[fn:1] being the most
> interesting, but a similar code is available for PubMed[fn:2].
> Unfortunately, being limited to certain fields, I am personally not able
> to adopt either. It would be great to have an interface to a general
> academic search engine (Google Scholar, ugh?).
Agreed. Google Scholar citations need very close proofreading, as they
can be erroneous or poorly formatted. I would submit that one should
never use a Google Scholar citation without checking it carefully
against the article or book to which it refers. An advantage of Google
Scholar, however, is that it offers skeletal bibtex entries for books
and articles in a wide variety of fields, whereas many of the databases
accessed by bibsnarf are limited to math and sciences. Since I use
biblatex together with the Chicago Manual of Style, any bibtex entry I
clip has to be edited and tweaked substantially. (Indeed, manual editing
is unavoidable when using biblatex.)
FWIW, here's my workflow:
1. Clip a bibtex citation or unformatted bibliographical data using
org-capture and conkeror or emacs. (This generates a timestamp and a
link to where I first found the reference --- very useful data for
reviewing one's own research habits and sources.)
2. Download the pdf, if possible (or make a todo to get/read it later).
3. While in the capture buffer, use org-attach to move the pdf quickly
from ~/Downloads to the attachments directory (this is much faster
than it sounds).
4. Create or correct a bibtex source block within the org entry.
5. Make a TODO to read the pdf. :)
Later, when I read the document, I proofread the bibtex entry once again
and call a function that moves it to a centralized bibtex file, leaving
a link in its place. As a rule, any citation that goes into my official
bibtex file *must* be correct and complete. Reftex, another of Carsten's
ingenious creations, is very handy for creating links to the citation
while taking notes.
For my own purposes, there would be little point in automating this
process, as any pdf I download needs to be inspected manually and any
bibtex entry I clip needs to be proofread and tweaked. The process
itself forces me to check every citation for accuracy.
Best,
Matt
next prev parent reply other threads:[~2011-03-29 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 15:47 zotero (or mendeley) integration with org Stephen Eglen
2011-03-26 21:04 ` Cian
2011-03-26 21:06 ` Ramon Diaz-Uriarte
2011-03-28 9:14 ` Stephen Eglen
2011-03-28 14:07 ` brian powell
2011-03-28 17:06 ` Erik Hetzner
2011-03-29 3:32 ` Matt Lundin
2011-03-29 7:21 ` William Gardella
2011-03-29 10:55 ` Rasmus
2011-03-29 11:42 ` William Gardella
2011-03-29 13:14 ` Matt Lundin [this message]
2011-03-31 11:39 ` Stephen Eglen
2011-03-31 20:13 ` Matt Lundin
2011-04-02 1:40 ` Alan E. Davis
2011-04-02 13:19 ` Matt Lundin
2011-04-02 13:37 ` Eric S Fraga
2011-04-02 14:13 ` Alan E. Davis
2011-03-30 0:54 ` Alan E. Davis
2011-03-30 8:26 ` Cian
2011-03-30 14:34 ` Joost Kremers
-- strict thread matches above, loose matches on Subject: below --
2011-03-27 3:12 Rustom Mody
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=8739m6oyqf.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus.pank@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).