representation of clients

representation of clients

[Richard Riley]

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?

In my case I'm writing some SW for a few small companies and am humming
and harring on how best to model the work process, requests, meetings
and cases which arise.

Any pointers/ links appreciated.

-- 
googletalk/jabber : rileyrgdev@googlemail.com

Re: representation of clients

[Russell Adams]

I'd suggest a file each. Agenda easily compiles schedules from
multiple files. Remember mode as well.

On Mon, Sep 07, 2009 at 05:20:24AM +0200, Richard Riley wrote:
> 
> 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?
> 
> In my case I'm writing some SW for a few small companies and am humming
> and harring on how best to model the work process, requests, meetings
> and cases which arise.
> 
> Any pointers/ links appreciated.
> 
> -- 
> googletalk/jabber : rileyrgdev@googlemail.com
> 
> 
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
> 


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

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

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

Re: representation of clients

[Sebastian Rose]

Richard Riley <rileyrgdev@googlemail.com> 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?
>
> In my case I'm writing some SW for a few small companies and am humming
> and harring on how best to model the work process, requests, meetings
> and cases which arise.
>
> Any pointers/ links appreciated.


While you could use this model:

  1. Add all your tasks to just one file.
  2. archive everything that is billed and payed.


I prefer to use one file for my personal agenda, and one per
customer. Those files tend to grow to more than just a few hundred
lines, and it's easier to find a task in the future.

Todo files for active projects/customers are added to my list of agenda
files (`C-c ['). That way it's easy to find the file by pressing `C-,'
repeatedly (e.g. during a phone call). You can type `C-,' with one hand
easily.

If the project/customer is not active anymore (nothing else to do), I do
a `C-c ]' to remove the file from my list of agenda files. This keeps
the agenda fast and clean.




   Sebastian

Re: representation of clients

[Bernt Hansen]

Richard Riley <rileyrgdev@googlemail.com> 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