From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: representation of clients Date: Mon, 07 Sep 2009 21:27:15 -0400 Message-ID: <87y6oqtedo.fsf@gollum.intra.norang.ca> References: <4aa47bfa.0b38560a.15f1.42f4@mx.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MkpUS-0005Gw-SR for emacs-orgmode@gnu.org; Mon, 07 Sep 2009 21:27:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MkpUO-0005Dk-RL for emacs-orgmode@gnu.org; Mon, 07 Sep 2009 21:27:24 -0400 Received: from [199.232.76.173] (port=43846 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MkpUO-0005Dd-Mo for emacs-orgmode@gnu.org; Mon, 07 Sep 2009 21:27:20 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:56951) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MkpUO-0004uv-Fn for emacs-orgmode@gnu.org; Mon, 07 Sep 2009 21:27:20 -0400 In-Reply-To: <4aa47bfa.0b38560a.15f1.42f4@mx.google.com> (Richard Riley's message of "Mon\, 07 Sep 2009 05\:20\:24 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Richard Riley Cc: Emacs-orgmode mailing list Richard Riley writes: > People using org-mode to maintain tasks, order, reminders , notes etc, > how do you represent clients? By a TAG? by a separate category? Separate > file? All of the above. http://doc.norang.ca/org-mode.html#sec-2.3 I tend to keep one file per client, with a #+FILETAGS entry for the client and set the category just so it's easy to see in the agenda what tasks apply to what client. I use the category to visually see what client a task belongs to on the agenda quickly. I use tags to filter tasks on the agenda. I use entire files to group tasks for a client so they can be added/removed from the agenda easily. So for every client project file I'll have the main file and an archive file to keep the entire history of whatever I've worked on in the past. Archive dead stuff to keep the agenda response time fast. Adding and removing clients from the agenda is simply adding and removing entire files from org-agenda-files. I have a client X that has multiple clients (A, B, C, D, etc), and I work on their client's systems. In this case I have org files X-A.org, X-B.org, ... , X-D.org since their clients come and go and I want to only keep the stuff I work on in my agenda. Similarly I'll also have an X.org for stuff specific to the main client that I work for. Hope some of that makes sense :) -Bernt