[willcarter]

If oo4 had filters, I would think of the app as a somewhat different tool from how I think of it today. That may not be a bad thing. Who would reject extra features in their favorite software?

But it does prompt other questions -- when does an outlining tool start to become a database, which is what the example of the large collection of recipes sounds like. When an outliner gets columns, we start to think of it as a spreadsheet. How long before we start asking for ever more complex Excel-like functions to calculate and validate column values? In another thread, I ask about a word count feature, which may be another example of the same thing.

At what point do enhancements become scope creep? While the company must continue to improve the power of the products, they will also be aware of the danger of turning a high quality outliner into something perceived as an under-powered spreadsheet or weedy database.

I enjoyed the OP's post but instead of dwelling on the inadequacies of OO, he/she may want to ask whether an outliner is the right tool for storing and manipulating a large collection of recipes, along with an ever-expanding mass of peripheral data.