emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: Jay Dixit <dixit@aya.yale.edu>
Subject: Re: using org-refile to sort research notes?
Date: Sun, 27 Apr 2014 17:54:37 -0700	[thread overview]
Message-ID: <87r44iqnn6.fsf@berkeley.edu> (raw)
In-Reply-To: CAGE7GqBgiXjy1hSNGoKmj2eXaYwU_UDjPrDC=DO8r7jO5dY_dQ@mail.gmail.com

Hi Jay,

Jay Dixit <dixit@aya.yale.edu> writes:

> Hello friendly org-mode community,
>
> I'm using org-mode to research and write a nonfiction book. I have a large
> amount of notes and quotes that I now need to sort into separate files.
>
> I am creating separate org files, one for each chapter of my book—
> chapter-1.org, chapter-2.org, etc.—with org headings in each one for every
> topic/subsection.
>
> I now want to categorize my notes, moving them from where they are—i.e. in
> a set of long, unorganized org files with names like new-research.org and
> more-research-and-notes.org—into the the chapter files.
>
> 1. Am I right in thinking that org-refile is the most efficient way to do
> this?

That sounds right to me.

> 2. What's the best way to do this? Should I add all of my chapter.org files
> to the agenda using org-agenda-file-to-front? I ask because these are not
> TODO headings, just headings with notes and quotes, so I'm not sure if
> using org-agenda functionality is appropriate.

Rather than adding these files to the agenda, I would have a look at the
`org-refile-targets' variable.  This variable tells Org where to look
for entries to refile under.

If this is a one-time operation, you may be able to just set the
variable a few times: adjust the variable to point to your chapter-1.org
notes heading, then refile all those notes; then point it to your
chapter-2.org notes heading, then refile all those notes...; etc.  This
will make it super easy to get the right refile target.

> Thanks in advance for any advice.

I don't know what led you to choose the new file layout that you're
moving to, but here is an alternative that you might also consider.

Make your project into just two files, say book.org and notes.org; the
first contains the text of the book, while the second contains the notes
and tasks for each chapter.  One advantage of this setup is that it
would allow you to organize your notes in whatever way is most natural
to them, rather than by chapter.  You can then use tags to associate
notes with chapters.  If for example you have some quotes that belong
together but are relevant to both chapters 1 and 2, you can have them in
a single entry in notes.org, tagged with :ch1:ch2:.  Likewise for tasks:
if some tasks require you to modify multiple chapters, you just tag them
multiple times.  (Links may also be helpful in this setup.)

I used to have a setup a lot like the one you described, but I found
that tags allowed me to organize my notes and tasks with much more
flexibility than using a tree-like hierarchy.  There's always the
question of where some note belongs when you can only file it in one
place.

I now use the two-file setup for writing my dissertation.  I keep tasks
and notes about readings I do in one file, with tags to associate them
with chapters and so on, and do my actual writing in another file.  This
keeps both types of information clean and organized, but I can move
easily between them.

--
Best,
Richard

  parent reply	other threads:[~2014-04-28  0:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-27 22:25 using org-refile to sort research notes? Jay Dixit
2014-04-28  0:25 ` Alan L Tyree
2014-04-28  0:54 ` Richard Lawrence [this message]
2014-05-06 23:05 ` Kyle Meyer
  -- strict thread matches above, loose matches on Subject: below --
2014-05-05  6:17 Jay Dixit
2014-05-05  9:40 ` Leonard Avery Randall
2014-05-07 14:40 Alfaro-Murillo, Jorge

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=87r44iqnn6.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --cc=dixit@aya.yale.edu \
    --cc=emacs-orgmode@gnu.org \
    /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).