[joelande]

Very well illustrated.

I have to agree I have the same problem and set of circumstances.

When I started with OF, I had LOTS of contexts: some were software-application based (GoLive, FileMaker, PowerSchool, PhotoShop, Server Admin, Parallels, etc), some were concept based (Budget, Network, etc).

That wasn't working. So, I parred down (at the time I came across an article of 43folders about simplifying contexts, and it seemed to fit with many of the problems I was having).

So I simplified, and I know have a minimal, more broad-in-scope set of contexts:
@Work
----office
----calls
----E-mail
----Agenda
--------CoWorker A
--------CoWorker B
----Waiting
--------CoWorker A
--------CoWorker B
@Errands
@Home
@Reading
@Training

I use the outer-level for general assignment, for example:
(1) I can often work at home, so that type of work is simply assigned to "@Work", and can be done at the office or at home, whereas tasks that need to be done at the office, get the assignment "@Work: Office"

(2) General agenda items will simply be assigned "@Work:Agenda", but colleagues that I frequently work with get the more specific assignment "@Work:Agenda:CoWorker A"

So I can click on "@Work" and see all work-related items, including what I could potentially work on at home, and I can click on "@Work:Office" and see things that HAVE to be done at the office, however I cannot EXCLUDE the "@Work:Office" items when I am working at home.


It is working better than the long list of specific-context items, I started with; but I still feel it is not working the way I would think it should conceptually. So far teh only thing that I see as a solution is tagging and/or multiple contexts.

I struggle with exactly what you posted, and totally relate to what you posted. The above probably didn't help you with solution, as I don't feel it is working perfectly for me either, but I wanted to at least let you know I feel your pain (and hopefully the developers will see this too).