-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Comments
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 |
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. |
Happy to re-open this if it becomes a fully fleshed out SIP. |
[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
Please let me know if you are interested and I would spend some time to work out the details.
The text was updated successfully, but these errors were encountered: