Dashboard requirements discussion

[yoid2000]

We'll need to select a dashboard for the project

Here are some thoughts for discussion:

• Open source
• Plus if the dashboard can work directly over the cloak odbc interface
  • On other hand, max flexibility if dashboard lets us write the resulting queries...
• We will give limited control to users (mostly selecting columns, and filtering on column values with col = val or col IN (val1,val2...)
  • As such, the dashboard primarily needs to work for these simple use cases. Maybe ok if the dashboard doesn't play well with aircloak for all possible uses...?
• We want good geo-location features. For instance
  • mapping zip-codes or parts of zip-codes into long/lat
  • drawing maps according to zipcode of part of zipcode boundaries
  • want contour/heat maps
• Customer will need to be able to configure dashboard

[sebastian]

Customer will need to be able to configure dashboard

By "customer" you mean the user or the entity using the dashboard?
I think this should not be a goal for the time being. Let's get something small and simple out first. Allowing customization is much harder.

[yoid2000]

By customer I meant the operator of the service.

Agree it is not a priority for the MVP...