-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Finding the best dataset is hard #63
Labels
Comments
@yosefw shouldn't this be 3 separate "issues"? |
I believe an issue is the problem, not the solution :-) |
@yosefw in general you're right, but in this case "issue" is just the moniker github used ;-) |
robotblake
pushed a commit
to robotblake/redash
that referenced
this issue
Apr 19, 2017
washort
pushed a commit
to washort/redash
that referenced
this issue
Dec 8, 2017
washort
pushed a commit
to washort/redash
that referenced
this issue
Dec 13, 2017
washort
pushed a commit
to washort/redash
that referenced
this issue
Jan 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Finding/browsing datasets is hard. The queries screen has too much technical data and not enough content data. In addition, in many cases there are many "overlapping" queries for the same or similar datasets.
Solution
The text was updated successfully, but these errors were encountered: