Add ADR for data exploration options #950
Conversation
| 2. We could provide the SQL to query the current set of data being displayed to | ||
| the user which can then be copy/pasted into Redash or BQ console as a | ||
| starting point for further exploration | ||
| 3. We could link directly to Redash with the query pre-populated |
There was a problem hiding this comment.
Option 3 is pretty much a non-starter... given the BI tool evaluation that is currently happening, we don't know what role Redash will serve going forward, investing in a tighter integration with Redash would be unwise right now.
|
|
||
| Extra options we can provide: | ||
|
|
||
| 1. We could provide other alternate data file formats (e.g. CSV) |
There was a problem hiding this comment.
This could make sense, but IMO only if we identify a concrete workflow that we're trying to serve, which would require some user research / interviews to find out. Are there specific product managers who would like to load the data into Excel to do further crunching? If yes, then adding CSV export sounds great! But we probably shouldn't build it unless we know there's a demand for the format(s) we're adding.
| Extra options we can provide: | ||
|
|
||
| 1. We could provide other alternate data file formats (e.g. CSV) | ||
| 2. We could provide the SQL to query the current set of data being displayed to |
There was a problem hiding this comment.
This seems to me the most useful initial deliverable.
There was a problem hiding this comment.
Also discovered this today: #634
robhudson
force-pushed
the
adr-data-exploration
branch
from
6a32f73
to
f641efb
Compare
robhudson
force-pushed
the
adr-data-exploration
branch
from
f641efb
to
4f332ee
Compare
No description provided.