From: Matthew Lundin <firstname.lastname@example.org>
To: Graham Smith <email@example.com>
Subject: Re: Orgmode for research information management
Date: Tue, 23 Jun 2009 10:29:46 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Graham Smith's message of "Tue, 23 Jun 2009 09:06:41 +0100")
Graham Smith <firstname.lastname@example.org> writes:
> I would be interested in any insights into how people use orgmode for
> information management eg. gathering information for scientific paper.
Org-mode is very well suited to this purpose. I like to think of
org-mode as an outliner with the functionality of a database. Each
outline heading/subheading is a node to which all sorts of metadata can
be attached. Thus, notes can be as free-form or as structured as the
project requires. The structure can emerge as the project progresses.
When beginning a research project, I dump a lot of material into a new
org file, making heavy use of org-remember and org-protocol. I tag items
as they come in, so I know that I'll be able to find them easily later.
I also create links to relevant files (pdfs, images, etc.). And any time
I need to follow up on something, I create a todo. Indeed, todo state
changes are immensely helpful for keeping track of what I've done so
My citations are located in a bibtex database; org-mode is able to
create links to individual items via org-store-link or org-remember. I
make sure to add a link to every outline heading, whether it be to a
website, a bibtex item, a file, or to some other node in the outline
(via <<internal-links>> or ID properties).
The beauty of org-mode is that I can organize my outline only when the
need arises. Thanks to tags, searches, and sparse trees, I can easily
find individual notes. And thanks to hyperlinks I can travel quickly to
the source of the information.
Anytime I need a more structured database, I create one within the
outline by using properties and column views. Let's say I need to keep
track of sources I've looked at an archive. I can easily create a
mini-database for the archive.
* Some Archive
:COLUMNS: %25ITEM %10TIMESTAMP_IA %17collection %6doc-number %18author %25title %10origdate %TAGS
** An old letter :industrialization:letters:
:collection: Personal Letters
:author: Michael Smithson
:title: Letter to brother
Some notes about the letter here...
[2009-06-23 Tue 09:37]
So an individual org outline can contain numerous custom databases! The
possibilities are endless.
And, of course, at any point I can export any part of the outline to
pdf, html, ascii, etc.
Hope this helps.
next prev parent reply other threads:[~2009-06-23 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 8:06 Orgmode for research information management 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 12:51 ` Graham Smith
2009-06-23 15:29 ` Matthew Lundin [this message]
2009-06-23 15:44 ` Graham Smith
2009-06-23 19:16 ` Eric S Fraga, Eric S Fraga
2009-06-23 19:31 ` Graham Smith
2009-06-23 23:30 ` Sebastian Rose
2009-06-23 23:37 ` Graham Smith
2009-06-24 21:27 Shrutarshi Basu
2009-06-25 12:20 ` Greg Newman
2009-06-25 15:27 ` Alexander
2009-06-25 16:00 ` Shrutarshi Basu
2009-06-25 17:08 ` Bastien
2009-06-25 17:19 ` Graham Smith
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 \
* 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).