emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "François Allisson" <francois@allisson.co>
To: Victor Miller <victorsmiller@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Organizing a collection of papers
Date: Mon, 4 Jun 2012 12:37:24 +0200	[thread overview]
Message-ID: <20120604103724.GA7773@francois-AOA150> (raw)
In-Reply-To: <loom.20120604T025637-979@post.gmane.org>

Hi Victor,

Le lundi 04 jun 2012 à 00:57:53 (+0000), Victor Miller a écrit :
> I've just started using org-mode, and so far find it quite
> useful. I have a very large collection of technical papers in a
> directory tree, and I'd like to go through them and index them
> through org-mode. What I'd like is to have a way of going through
> them and look at the unannotated ones, and annotate them one by
> one. I imagine doing this by first making up a file of links like
> [[xxx.pdf][not done yet]], 

The script dir2org.zsh (located in the contrib/scripts directory) may
be a good starting point for you.

It transforms (recursively) a directory and all its files into an Org
mode file reproducing the directory tree hierarchy with one headline
per file, and it creates automatically the links to the files.

Briefly, if your files are located in the directory ~/my-big-database
(and its sub-directories), just type:

- cd path-to-org-mode-distribution-directory/
- cd contrib/scripts
- zsh    (if, like me, zsh is not your usual shell, you must call it,
          eventually install it; at the end, type "exit" to return to
          your favourite shell)
- ./dir2org.zsh ~/my-big-database > orgfile.org

And it's done. Your "orgfile.org" contains linked headlines for
all your files. You can then start playing with your files with all
the Org mode facilities (tags, ordering headlines, adding properties,
annotations, todos, etc.). HTH.

> and then being presented with the not
> done ones, glancing at them and deciding how what annotations to
> put in. In addition I'd like to add tags. What I'd really like is
> to be able to make up new tags on the fly. Has anyone done
> anything like this in org-mode?

I don't know what will be the better workflow to achieve this. I think
we are all looking for the best workflow to handle our electronic (and
non electronic) libraries. 

I cannot say yet what my workflow is, because I'm currently working on
it. FWIW, I /was/ handling my bibliographic resources in a big BibTeX
file, adding custom BibTeX fields for my personal needs. I can only
give hint whither I am going:

- a big biblio.org file with a lot of headlines (one per item),
  with three custom todo keyword (in a sequence TOREADLATER TOREAD |

  - TOREAD: for items on which I still have something to do (read,
    annotate, decide whether it is worth reading or not, or if I
    should do something with it, etc.). These appear in my custom
    agenda-view as a block name "Currents readings".

  - TOREADLATER: idem. But these items do *not* appear in my custom

  - READ: for items on which I'm done.

- each item has a name "Author (year) Title of document", it contains
  tags as keywords, BibTeX properties (using org-bibtex.el), custom
  properties (physical location if not electronic, date of insert,
  etc.). It contains link to file (if file). And it contains my
  reading notes, quotes, comments, TODO items (if I have to check
  something, or discuss something with someone, I plan it). All this
  using sub-headings (for respecting chapters, or the papers
  structure, or other subdivision for my own needs. As this file is in
  my org-agenda-files, I can take advantage of all Org mode

I can export the whole database as a BibTeX file using only one
command (M-x org-bibtex, thanks to the excellent org-bibtex.el), and
can use it in my Org mode files (formerly LaTeX files), using the
(new) latex exporter.

I can also export a headline with the (new) exporter to share my notes
on one item with someone (and easily decide which parts of the notes
not to share with a few :noexport: headlines)

When I have free time (...) or when (I recommend doing this) I
scheduled reading hours in my week, I just call my custom agenda
command, showing me only TOREAD items, I'm one space key away from my
biblio.org file, and I can just fill my notes while reading.

I decided to restrict myself to 5 TOREAD keywords. Once a TOREAD is
done, it becomes READ and disappear from my agenda view. Once my
TOREAD list becomes empty, I decide which TOREADLATER becomes TOREAD
(again with the rule of 5). It helps me not starting dozens of things and
never finish them...

As for the capture of new items, I'm still working on it. I started to
use the command "M-x org-bibtex-create" for new items, and then
arrange manually my other needs, but I'm now in the process of
creating custom org-capture templates to better achieve my needs.

I would happily share a less confused state of my workflow when I'll
be more happy with it.

Sorry for being such OT.

> Victor

Good luck with your collection of papers,


  parent reply	other threads:[~2012-06-04 10:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  0:57 Organizing a collection of papers Victor Miller
2012-06-04  8:41 ` BernardH
2012-06-04 10:37 ` François Allisson [this message]
2012-06-29  0:24 ` Frank
2012-06-29  4:33   ` John Wiegley
2012-06-29 16:07     ` Thomas S. Dye
2012-07-03  0:46       ` Christian Wittern

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=20120604103724.GA7773@francois-AOA150 \
    --to=francois@allisson.co \
    --cc=emacs-orgmode@gnu.org \
    --cc=victorsmiller@gmail.com \


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