I wanted to propose another situation where multiple, non-hierarchical, OR contexts would be useful. It's very similar to the "shopping" scenario, but it's not shopping. It's essentially a research task.
Let's say that I have:
Project: Choose plants for the experimental low-water bed.
Next Task: Get a real-world look at Shasta Daisy "Becky".
Let's say that I know that "Becky" can be seen at:
- The city park.
- Jane's garden.
- Grafton Nursery Display Beds
Each of these sites is sufficient. Each is equal. There is nothing to make one preferable to the others. As far as I can tell, there _is_ no single best context here. And the contexts are not in any way hierarchical.
But so far, for this one task, I can solve the problem by simplifying - I can just put the task in Errands, and scan Errands everywhere I go, and be reminded to go look at "Becky".
However, let's say that I want to look at real-world examples of sixty-seven other plants. Or eight-four. Or three hundred.
And let's say that I already called around, got plant lists, got brochures, checked web sites, to find out where those plants can be seen. Let's say that I have seventeen locations where I can look at plants, each of which has a varying number of of these plants on display, with lots of duplication. I want to put this information in OmniFocus, sync it to my phone and, whenever I'm at one of these locations, get a look at the plants available at the location, so that I can photograph them and take notes.
In this case, I want lists for each location, and I want to build these lists with multiple contexts, one context for each location. Checking off a plant in any context should check it off altogether. I don't see any graceful way to handle this other than multiple "OR" contexts, or using another tool entirely.
When I go to the city park, for example, I don't want to look through all sixty-seven (or three hundred) plants in one "Plant Viewing" context and check the task detail below them to see if that plant should be at the city park. I already did that work, and I don't want to do it again. By the time I get to the city park, I should be done fumbling with my lists; I want to be down to glancing at the list, taking photos and scribbling notes, and checking items off.
I could eliminate that problem by duplicating the tasks, so that all three places that are growing "Becky" have "Becky" in their list, for three separate tasks. I don't like that either. I don't want to have to search the checked-off items for places I've already been, or dig through my notebook, to see if Becky was checked off, and i don't want to waste time hunting down Becky two or three times before I remember, in an annoyed and frustrated way, that I have indeed seen Becky. If I only have a dozen plants to look at, it may not be a problem to remember what I've seen, but sixty-seven or three hundred is starting to push memory, and isn't the whole point that I don't have to remember all this stuff myself?
I also don't want to do a bunch of extra pre-work planning, making a battle plan where each plant is listed at only one location. This is because (1) I may not go to the locations in the order that I predict and (2) my information may be out of date and "Becky" may have just been mowed down at the city park, so that I need to look at it when I get to Jane's garden after all. Or, even worse, I skipped it at Jane's garden because it wasn't on that list in the battle plan, so that when I find it's been mowed down at City Park, I have to go back to Jane's.
I could just have one task called "Look at plants" and store the individual tasks outside Omnifocus altogether. I don't like that either - I've just essentially made a project into a single task, and totally eliminated the value of contexts, plus I now have to get another tool to sync politely to my phone. For now, yes, I could have a task for the City Park context that says, "Check the SomeOtherSoftwarePackage list of plants for City Park", but I'd rather do it all on one tool.
This is essentially the "shopping" task all over again, but I think that there may be _many_ "shopping"-like tasks - shopping, research on things that might be available at many locations (like the above), activities available at many locations (going to movies is a simplistic case that could admittedly just stay in Errands), and so on.
Anytime that you have the situation where there are several functional instances of a resource, but not _so_ many instances that you can count on finding that resource absolutely anywhere, there's a possibility that multiple OR contexts may be useful. Bird watching. Research in rare books. Viewing rare but multi-instance art, like prints. Purchasing niche products. All of these examples are strongly location-based, but I'd bet that there are other context types that would apply, if I could just think of them. :)
This type of project may be rare enough to keep multiple contexts from floating to the top of the priority list for features, but I think that they exist, they're legitimate, and multiple OR contexts would be genuinely useful for them.
Gardener