The Omni Group
These forums are now read-only. Please visit our new forums to participate in discussion. A new account will be required to post in the new forums. For more info on the switch, see this post. Thank you!

Go Back   The Omni Group Forums > OmniFocus > OmniFocus 1 for Mac
FAQ Members List Calendar Search Today's Posts Mark Forums Read

Structure for iterative Projects (I'm new to O-Fo) Thread Tools Search this Thread Display Modes
What is the best way to structure a Project that is:
- repeated regularly
- contains Actions that are themselves repeated _each time done_ on a number of different items?

I'll attempt a general example: research on the Web.

Daily Cull of News Articles
- Open Browser
- Scan News Aggregator
- - Um ... Make list of sites to check?
- Go to site
- Log in if required
- Search for articles on topic
- Download article when wanted.
- - Separate downloads into Finder folders by site
- log out
- Go to next site ???
- Repeat till done with sites on list
- Repeat with list of sites/articles from lecture
- Process downloads

As best I can tell, I'm totally confused about the best way to translate conditional branching (If/then) and "repeat till done" processes into Projects and Actions.
Are you perhaps over-specifying the steps in the Project and thereby leaving yourself no room even to breath (or take a bathroom break or chat on the phone or ...)?

In other words, think about how OF can be used instead to structure the OUTCOMES that help you reach an objective. Use fewer "set-in-stone" recipe-type actions and instead more outcome-directed actions, as below ...

Cull News Articles (repeat daily, start 8am, sequential)
- generate first cut of potential articles of interest (context: browser)
- cull first cut list to articles of primary importance (context: computer)
- collect articles of primary importance to storage (context: browser)
- finalize table of contents to daily collection (context: computer)

Originally Posted by DrJJWMac View Post
Are you perhaps over-specifying the steps in the Project and thereby leaving yourself no room even to breath (or take a bathroom break or chat on the phone or ...)?

No question about it -- but I have a reason: I'm learning how to use OFO, I want to know exactly how I can fold it before I commit to making flying swans, and I have always found that working on a small scale with exactitude is an excellent way to learn a skill prior to expanding its use.

Thanks for the useful and educational Project layout. 😊 .
I guess one way to do this with some gory details would be ...

Cull News Articles (repeat daily ...)
- open browser
- open news feeds
- (!) Cull This Specific News Article (Action Group, sequential, repeat immediately)
-- read Web page article
-- process Web page article (Action Group, sequential)
---- (*) accept Web page (Action Group, parallel)
------ store article
------ store link
------ ... whatever else
---- (*) reject Web page
-- close out news article view

The two tasks marked with (*) would have to be processed manually. You would manually delete the one that you decide not to do and complete the other.

The Action Group marked (!) would repeat itself for each news article. When you have exhausted the news articles, delete the entire repeat occurrence.


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Similar Threads
Thread Thread Starter Forum Replies Last Post
Advice on my structure kinderkouture Applying OmniFocus 7 2012-06-28 11:29 AM
BIG feature request: Change the whole structure of projects Mitch Wagner OmniFocus 1 for Mac 6 2011-10-20 11:58 AM
structure advice peterlemer OmniFocus 1 for Mac 1 2010-09-16 10:58 AM
Can I structure a document like this in OOP? rmathes OmniOutliner 3 for Mac 11 2010-01-04 10:05 AM
Help with project structure please? peterlemer OmniFocus 1 for Mac 6 2008-09-14 08:18 AM

All times are GMT -8. The time now is 06:53 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.