junlincc edited a comment on issue #14473:
URL: https://github.com/apache/superset/issues/14473#issuecomment-839135296
moving your great suggestions under this project @EBoisseauSierra
**Issue**
As a new user to Superset, I have been confused by the default behaviour in
the Explore mode.
### Suggestions
**Time section**
issue: By default, only “last week”'s data are used. This filter is applied
silently: a new user might not immediately notice that “Time range: Last week”
means some data are not considered. And this can be quite puzzling if one deals
with forecast (i.e. future) data, as the user then gets a “No Results” error.
suggestion: Don't apply filters by default — or if so, let the user know
about them.
**Query/Metrics section**
issue: By default, COUNT(*) is selected (as the only pre-defined “metric”).
This feels counter-intuitive to me, as I mostly know what chart I want to
build, and it's almost never using COUNT(*) as main KPI. I then have the
surprise/frustration of having a chart populated with something different from
what I have in mind.
suggestion: Could we prevent the chart from “trying to be smart”, and:
have “metrics” non pre-filled,
don't run the query straight away, but wait for the user to first specify
the chart/dashboard and them to click “run”.
The “Run” button could be greyed out/disabled as long as mandatory fields
for the chart aren't populated yet.
**Query/Metrics section**
issue: I don't want to be forced to chose an aggregate. Indeed, the data I
query are sometimes already “aggregated” (say I want to plot temperature over
time by location and I have only one reading per location and per hour (at the
*:00.000 timestamp)), and in that case “aggregating” seems counter-intuitive
(even if, I agree, SUM, AVG, MIN, and MAX would return the same value). Yet
when adding a Metric / Simple, the “Save” button is greyed out after I select a
column, until I choose an aggregate.
suggestion: Allow users to not select any aggregate, and fail if multiple
record for the same index are returned.
**Dataset / Columns panel**
issue: While most data types have an “icon” next to the column name (str ￫
ABC, timestamp ￫ 🕘 , int ￫ #), PostgreSQL “Double Precision” don't.
suggestion: Define an icon for it (same as float if exist, or something like
#.##)?
Customize / {x, y} Axis / {x, y} axis format input
issue: I have metrics that have a unit (e.g. physical dimensions). Yet I am
unable to specify this unit on the axis (e.g. .2f °C for temperature).
suggestion: Allow for adding arbitrary prefix/suffixes on top of the D3
formatting (… or provide an example in case it's already possible, as “some
users” — read: myself — haven't been able to find how to) — cf. #14550.
Customize / {x, y} Axis / {x, y} axis format input
issue: The axis formatting allow for custom user inputs (when one simply
type in the box). However, once one has typed a format string (say: ,.3f), it
is not possible to correct it (e.g. to change it into ,.2f). Indeed, as soon as
one type in the box again, the whole content is erased. This behaviour isn't
error friendly and force the user to memorize what was the previous format
string.
suggestion: Don't erase former input, but rather enable users to
amend/modify the existing value.
Explore a whole dataset
issue: First go to the Data/Dataset menu. Then when clicking on a given
dataset, the Explore panel opens. Yet the default query is basically SELECT
COUNT(*) WHERE (timestamp ≥ now() - 7 AND timestamp < now()), in the Table
chart's “Aggregate” query mode. As detailed above, this can cause some
confusion.
suggestion: Set default query to SELECT * (possibly appending a LIMIT 100)
and set the table in “Raw records” mode. Indeed, when I click on a dataset, I
expect to see what's inside, raw — not an aggregate.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
