emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: using org mode to help with a construction project
Date: Sun, 31 May 2020 10:58:08 +0200	[thread overview]
Message-ID: <20200531085808.GB23478@volibear> (raw)
In-Reply-To: <2866a396-d84f-d740-428d-900d8c6ac6a3@ramandgita.com>

On Sat, May 30, 2020 at 06:13:01PM -0700, Ram Bhamidipaty wrote:
> I am still a beginner at org mode - I am looking for ideas or
> information about how I can use org mode to help me manage a
> construction project.
>
> I have a list of contractors (name, phone, email, etc) that I want to
> contact - and eventually get bids. Right now I would like to keep track
> of which ones have been sent an initial email, a time stamp for that
> would also be good. Maybe even record any response.

Start with a text outline, since you're new to org. Try adding timestamps to
record when you did things with C-u C-c . (adding an inactive timestamp). Use
your header tags to record the state of things (TODO and DONE).

> If there were a nice way to select and export the contact info for
> certain contractors that would be nice. I have a list of around 40 and I
> want to contact them in batches of 5. Maybe I could pick 5, export the
> addresses to Thunderbird and send initial requests.

Treat it as all text for now while you're learning. Paste in their contact data
into a headline with them, and manage it that way. Create action items for them
underneath their entry.

Later you can get into things like drawers, column view, keywords, etc.

You're likely to always have to copy and paste out their contact data if you
aren't using an Emacs mail client.

Here's how I would start, in a fresh empty file.

* Construction Project

** Contractors

*** TODO BOB's Billy Goat Crew

Bob, 999-555-1212, off Blueberry Lane.

[2020-05-31 Sun 10:53]
Called bob today, and we discussed X, Y, and Z.

[2020-05-31 Sun 10:55]
Sent bob an email confirming our discussion, with points to follow up on

**** TODO Bob had a question

[2020-05-31 Sun 10:55]
Do we use nails or screws? Must check!

*** DONE Sleezy Todd's Emporium of Fraud

Todd, 888-555-1212, under the bridge by the tracks.

[2020-05-30 Sat 08:54]
Called on Todd today. He said he could deliver everything. Sounded too
interested. Made an appt.

[2020-05-31 Sun 10:55]
Visited Todd today, and I'm not impressed. I think he'd shortcut the work and
has no good prior examples. No longer considering him.


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3


      reply	other threads:[~2020-05-31  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31  1:13 Ram Bhamidipaty
2020-05-31  8:58 ` Russell Adams [this message]

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=20200531085808.GB23478@volibear \
    --to=rladams@adamsinfoserv.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: using org mode to help with a construction project' \
    /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

Code repositories for project(s) associated with this 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).