superset/TODO.md

49 lines
2.4 KiB
Markdown
Raw Normal View History

2015-07-15 13:12:32 -04:00
# TODO
2015-09-27 21:02:00 -04:00
List of TODO items for Panoramix
2015-09-22 19:53:06 -04:00
2016-02-04 20:01:40 -05:00
## Deep changes
* Use NPM for js management
* Use `requires`
* **Getting proper JS testing:** unit tests on the Python side are pretty solid, but now we need a test suite for the JS part of the site, testing all the ajax-type calls
2015-12-29 16:47:21 -05:00
## Features
2016-02-04 20:01:40 -05:00
* **Homepage:** a page that has links to your Slices and Dashes, favorited
content, feed of recent actions (people viewing your objects)
* **Stars:** set dashboards, slices and datasets as favorites
* **Comments:** allow for people to comment on slices and dashes
2015-12-29 16:47:21 -05:00
* **Dashboard URL filters:** `{dash_url}#fltin__fieldname__value1,value2`
* **Default slice:** choose a default slice for the dataset instead of default endpoint
2016-01-11 17:34:18 -05:00
* **refresh freq**: specifying the refresh frequency of a dashboard and specific slices within it, some randomization would be nice
2015-12-29 16:47:21 -05:00
* **Widget sets / chart grids:** a way to have all charts support making a series of charts and putting them in a grid.
the same way that you can groupby for series, you could chart by. The form fieldset would be common and use
a single field to "grid by", a limit number of chart as an N * N grid size.
2016-01-29 13:29:23 -05:00
* **Advanced dashboard configuration:** define which slices are immune to which filters, how often widgets should refresh,
2015-12-29 16:47:21 -05:00
maybe this should start as a json blob...
2016-01-29 13:29:23 -05:00
* **Annotations layers:** allow for people to maintain data annotations,
2015-12-29 16:47:21 -05:00
attached to a layer and time range. These layers can be added on top of some visualizations as annotations.
An example of a layer might be "holidays" or "site outages", ...
2016-01-11 17:34:18 -05:00
* **Worth doing? User defined groups:** People could define mappings in the UI of say "Countries I follow" and apply it to different datasets. For now, this is done by writing CASE-WHEN-type expression which is probably good enough.
2016-02-04 20:01:40 -05:00
* **Slack integration** - TBD
2015-12-29 16:47:21 -05:00
2015-12-29 16:47:21 -05:00
## Easy-ish fix
2016-02-04 20:01:40 -05:00
* CREATE VIEW button from SQL editor
* Test button for when editing SQL expression
* Slider form element
2015-12-17 19:26:36 -05:00
* datasource in explore mode could be a dropdown
2015-12-29 16:47:21 -05:00
* Create a set of slices and dashboard on top of the World Bank dataset that ship with load_examples
* [sql] make "Test Connection" test further, run an actual dummy query
2015-12-14 19:38:54 -05:00
* [druid] Allow for post aggregations (ratios!)
2015-12-17 19:26:36 -05:00
* in/notin filters autocomplete
2015-09-25 18:43:50 -04:00
2015-12-29 16:47:21 -05:00
## New viz
2016-02-04 20:01:40 -05:00
* Maps that use geocodes
* Time animated scatter plots
2015-12-29 16:47:21 -05:00
* Horizon charts
* Chord diagram
* ...
2015-12-14 19:38:54 -05:00
## Community
2015-12-29 16:47:21 -05:00
* Creat a proper user documentation (started using Sphinx and boostrap...)
2015-12-14 19:38:54 -05:00
* Usage vid