What might be the "right" way to do a sumbit-and-approve workflow in
calendar 4?
On our existing ACS 3.4 installation we (Ybos contracting for us)
added approved_p and approved_date columns to the cal_items table.
The workflow is typical ACS 3 "submit and wait for the admin" with a
UI similar to that provided by the enhanced-news package. Any
registered user can "suggest" an item for the global campus
calendar.
Since openacs4 uses acs-events we can't do this anymore. Do we
define a "shadow party" for each party that owns a calendar, and
switch parties on approval? Badly abuse the status_summary column?
Add approved_p/approved_date/approving_user_id columns to the core
acs_events table?
