• evidence that dashboard is more than a "simple table"
  • ...
• Atom Projection
  • can all the sorting really be done on the server, or does it have to be a weird hybrid
    • worried about recurrence

dashboard coordination

• server side processing of dashboard query - who is doing this work
  • bcm says "bcm or randy"
    • in which case mde, and (bcm || randy) need to talk
    • mde and XXX to figure out what exactly he needs from the server

• Topics
  • if need be, we can get away with not doing much here right now, but I'd still like to have some clean up done so that we don't introduce new code to have to rework
  • existing stuff works, but is not documented and is full of calendar specific language and shouldn't be in the ui code
  • bobby's plan for an incremental topic reworking (a plan that we can adopt in stages if need be)
    1. Figure out all existing topic calls, what they do. Replace unnecessary ones (if any)with simple function calls. If any are too granular, collapse several messages into one.
    2. "formalize" remaining topics - make document them, use constants, make api more consistent if need be, remove cal specific language
    3. where possible, remove topics from ui code, move to service layer

• Mde synced back up
  • Data model - mde needs a walkthorugh from br
  • br needs to document the data model code better
  • integration is still being worked on, but loading works (mostly)
    • • recommend holding on new update work (dashboard)