emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander <alejck@gmail.com>
To: Greg Newman <greg@20seven.org>
Cc: emacs-orgmode@gnu.org, Shrutarshi Basu <shr@basushr.net>
Subject: Re: Orgmode for research information management
Date: Thu, 25 Jun 2009 11:27:16 -0400	[thread overview]
Message-ID: <2e177a690906250827r404b40ecm713df77ba92fff6c@mail.gmail.com> (raw)
In-Reply-To: <71454fac0906250520s2959fcna213318bc526f242@mail.gmail.com>


I've recently started using org-mode to organize reading notes and to
write papers, and I'd be interested in this script too. One thing that
I have a little trouble with is connecting these three pieces of
information for each reference: bibtex key, pdf file with actual
article, and org file with notes.



On 6/25/09, Greg Newman <greg@20seven.org> wrote:
> Hey Basu.  I'd love to see this python script.  I'm a complete n00b with
> latex so i'm trying to get up to speed on it fast; however all my research
> on this has led me to believe this is the perfect setup and your description
> of your flow is confirming it more.
> Thanks,
> *Greg Newman*
> http://20seven.org
> twitter: 20seven
> On Wed, Jun 24, 2009 at 5:27 PM, Shrutarshi Basu <shr@basushr.net> wrote:
>> I just started using orgmode today to organize the papers that I'm
>> collecting for my own research. The way I work is a bit complicated, but I
>> like it. I have all my PDFs in a single directory and my notes in a
>> separate
>> directory. These notes are extensive outlines and notes for each paper.
>> Corresponding files are named the same in each directory to make it easy
>> to
>> relate the paper to the notes. I also have a bibtex file with citation
>> info
>> for each file. I then run a Python script over the two directories and the
>> bibtex file which generates an org file containing links to the PDF and
>> notes and some of the bibtex data (authors and publication). This file is
>> my
>> main interface to all my research info. I use Org-mode tags to do some
>> simple categorization and also store short notes. If you like, I could
>> give
>> you my Python script. Some of the file paths are hard coded in, but
>> they're
>> easy to change. You can also view PDFs directly in Emacs.
>> Basu
>> --
>> Shrutarshi Basu
>> Computer Science,
>> Electrical and Computer Engineering,
>> Lafayette College,
>> The ByteBaker -- http://bytebaker.com
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-06-25 15:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 21:27 Orgmode for research information management Shrutarshi Basu
2009-06-25 12:20 ` Greg Newman
2009-06-25 15:27   ` Alexander [this message]
2009-06-25 16:00     ` Shrutarshi Basu
2009-06-25 17:08       ` Bastien
2009-06-25 17:19 ` Graham Smith
  -- strict thread matches above, loose matches on Subject: below --
2009-06-23  8:06 Graham Smith
2009-06-23 11:06 ` Chris Gray
2009-06-23 11:51   ` Graham Smith
2009-06-23 12:41     ` Chris Gray
2009-06-23 15:29 ` Matthew Lundin
2009-06-23 15:44   ` Graham Smith
2009-06-23 19:16     ` Eric S Fraga, Eric S Fraga

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:

  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=2e177a690906250827r404b40ecm713df77ba92fff6c@mail.gmail.com \
    --to=alejck@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=greg@20seven.org \
    --cc=shr@basushr.net \


* 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


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).