Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SIP] Add a top level data navigation to each chart #12725

Closed
wernerdaehn opened this issue Jan 25, 2021 · 3 comments
Closed

[SIP] Add a top level data navigation to each chart #12725

wernerdaehn opened this issue Jan 25, 2021 · 3 comments
Labels
dashboard:drill-down Related to drill-down functionality of the Dashboard dashboard:native-filters Related to the native filters of the Dashboard data:connect:drill Related to Drill sip Superset Improvement Proposal

Comments

@wernerdaehn
Copy link

[SIP] Add a top level data navigation to each chart

Motivation

Slice and dice is done by the chart consumer, not only(!) the chart developer.

I have been working for Business Objects and SAP and I am in the Business Intelligence Market for more than 20 years. I feel that the filter concept is too technical, the navigation within the data not suited for self service BI.

Imagine the FLIGHTS data in a real world scenario. You create a chart with the flight delays and this chart has certain configurations, e.g. group by AIRLINE, flight date is the time component. You might add filters as well, e.g. last year and delay >10 minutes.

If the created chart has a drop down box for each (useful) attribute above it, the user can easily move within the data. One drop down box is called ORIGIN_AIRPORT and shows the list of all airport codes to select from. Another are STATE, COUNTRY, DISTANCE,... all by which analyzing the data makes sense. "Show me the delays for one airport", "Should I pick SFO or San Jose?", "Does the time of the day play a role?"

The main problem of such navigation bar is that a normal table/view has thousands of columns the user might want to navigate within the data. This is when hierarchies come into play. In above example the COUNTRY, STATE, ORIGIN_AIRPORT are related to each other. It does not make sense to filter on a specific airport and then offer to filter the country also. Instead of rendering each attribute individually the attributes are organized in hierarchies:
COUNTRY->STATE->AIRPORT
Then the Location-of-Departure hierarchy dropdown is opened, at the first level all countries are shown. The user can select one country or multiple (checkboxes!) or expand one country to see its states etc.

Proposed Change

  1. On top of each chart is a horizontal, scroll-able list of columns the user might want to navigate within. This list contains attributes and measures.
  2. Depending on the type of element different selectors are shown. For attributes like names a checkbox is rendered to select/deselect. For attributes that have an order like a date/time a from-to range selector is shown. Long/Lat has a rect shape selector,...
  3. In the table definition hierarchies can be defined to group attributes together. Such hierarchies can either be
    • based on columns: GEOGRAPHY hierarchy is from COUNTRY to STATE to AIRPORT
    • based on parent-child relationships: PRODUCT_GROUP, PARENT_PRODUCT_GROUP
    • can contain alternative hierarchies also: GEOGRAPHY has an alternative using LONG/LAT columns
    • can be generated: TIMESTAMP has YEAR->MONTH->DAY->HOUR and as alternatives: WEEK, WEEKDAY, WORKDAY, QUARTER,...
  4. It would be nice if the drop down list is sorted by relevance. For example you might have filtered on a regional airport and the plane type selector lets you chose a 747? Nothing is more demotivating as constantly getting a no-data chart.
  5. Similarly showing the impact of a filter. If each filter value hints how much it will modify the diagram, e.g. airport1 has lots of delays, airport2 none that would help the user also.

Please let me know if you are interested and I would spend some time to work out the details.

@zuzana-vej zuzana-vej added the dashboard:native-filters Related to the native filters of the Dashboard label Apr 20, 2021
@zhaoyongjie zhaoyongjie added data:connect:drill Related to Drill dashboard:drill-down Related to drill-down functionality of the Dashboard labels Jun 10, 2021
@stale
Copy link

stale bot commented May 1, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label May 1, 2022
@rusackas rusackas added the sip Superset Improvement Proposal label Jun 7, 2023
@stale stale bot removed the inactive Inactive for >= 30 days label Jun 7, 2023
@rusackas
Copy link
Member

rusackas commented Jun 7, 2023

This seems to have slipped between the cracks. If you'd like to pursue this as a SIP, please fill out the remainder of the SIP template and post it to the dev@ emailing list. Otherwise, if you'd like to continue seeking community support of this feature request, please open a new Ideas thread in our Github Discussions area.

@rusackas rusackas closed this as not planned Won't fix, can't repro, duplicate, stale Jun 7, 2023
@rusackas
Copy link
Member

rusackas commented Jun 7, 2023

Happy to re-open this if it becomes a fully fleshed out SIP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dashboard:drill-down Related to drill-down functionality of the Dashboard dashboard:native-filters Related to the native filters of the Dashboard data:connect:drill Related to Drill sip Superset Improvement Proposal
Projects
Status: Denied / Closed / Discarded
Development

No branches or pull requests

5 participants