emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher W. Ryan" <cryan@binghamton.edu>
To: emacs-orgmode@gnu.org
Subject: still struggling with workflow
Date: Thu, 06 Sep 2012 14:48:00 -0400	[thread overview]
Message-ID: <5048EFE0.4080702@binghamton.edu> (raw)

I've been using org-mode for, oh about a year now, and it seems like a
very useful tool. But I'm still struggling to understand and implement
effective workflows for projects, re-using bits and pieces of text.

For example, I have a general project related to heat wave morbidity and
mortality, and indoor heat index. Hopefully I can parlay it into a
number of distinct studies, each with IRB applications, grant
applications, and papers (all pdf output), and presentations (beamer pdf
output.)  For example, all my stuff for the first study is in a single
org file, HeatWaves1.org. The second project's documents will need to
re-use much of that material, but not all of it; and there will be some
new material.

Is it viable to keep everything related to my heat wave work, for all
substudies, in the one org file, and customize the output to my needs at
different times, via judicious use of headlines and :export tags?  Or is
it best to start a new org file for each substudy and copy/paste what is
needed from the old?


Christopher W. Ryan, MD, MS
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY  13904

"Once we recognize that we do not err out of laziness, stupidity, or
evil intent, we can liberate ourselves from the impossible burden of
trying to be permanently right. We can take seriously the proposition
that we could be in error, without deeming ourselves idiotic or
unworthy." [Karen Schulz, in Being Wrong: Adventures in the Margin of Error]

             reply	other threads:[~2012-09-06 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 18:48 Christopher W. Ryan [this message]
2012-09-06 19:43 ` still struggling with workflow Nick Dokos
2012-09-06 23:07   ` Jambunathan K

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=5048EFE0.4080702@binghamton.edu \
    --to=cryan@binghamton.edu \
    --cc=emacs-orgmode@gnu.org \


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