Not including Offline-focussed work, there are three different items:

1.  Add more possible states to status for various objects: parameters, 
configs, maybe ancillaries, maybe FSW_inputs..

 * get precise information from Greg about what's needed
 * determine if new fields are needed or new states in existing fields
 * if new states
     - everybody needs to be running latest rdbModel, which loosens
       compatibility requirements between MySQL tables and xml description
       of db
     - change MySQL columns currently defined as ENUM to VARCHAR(..) 
     - add new states to ENUMs in xml description

   else if new columns
     - add columns to databases
     - add column descriptions to xml

* In either case, get spec from Gregg or Eric G. on which state transitions
  are allowed; write supporting update routine(s)

2. History
  * Confirm with Bryson that proposed tables Acq_summary and Acq_mode 
    look ok.  Revise mootCore/maint/createAcq_summary.sql, 
    mootCore/maint/createAcq_mode.sql if necessary.  Add invocations of
    these files to createMOOD.sql
  
  * Create the new tables

  * Go over interface of 
     MootUpdate::updateAcqSummary(...) with Bryson

    Write it.

  * Go over interfaces of MootQuery::consistentKeys(..)
    MootQuery::findConfigCandidates(...) with Bryson
     
    Write

  * Consult potential users about addition queries; design; write.

3. CDM support