Just to second Andrew's suggestions regarding the need for workflow features to be applied to the Web Content Management process, perhaps as part of the Portal Tool Kit.

Andrew M. Kuchling wrote

For example, our workflow would look like this:

* Member creates a Run object * An MX staff member looks at the Run, makes some comments, and bounces it back to the member, who revises it. * MX staffer looks at the run again, and approves the revised version. * 3 other Members with a certain role look at the run and approve it. Various other people get notified about this.

The mind boggles at the covolutions that perfectly computer literate folks, programmers, admins, dbas, etc., come up with. A casual observer might conclude that the intention were to add as many steps and people into this process as possible. It's as if they've forgotten we have computers and messaging systems involved that might be able to help us build this Web thingy! I don't pretend to understand the UML Zen needed to map out the ideal solution, but as for nailing the problem, Andrew has done that. Thanks for keeping on, Jerry S.