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

Finding the best dataset is hard #63

Open
yosefw opened this issue Jan 23, 2014 · 3 comments
Open

Finding the best dataset is hard #63

yosefw opened this issue Jan 23, 2014 · 3 comments
Labels

Comments

@yosefw
Copy link

yosefw commented Jan 23, 2014

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

  1. Tags to queries (eg. product features)
  2. Advanced search for searching only in titles/descriptions/query
  3. Allowing users to mark other user's queries/datasets as of a 'high-quality' (similar to the Official Files feature on Yammer http://success.yammer.com/yaminars/manage-files/).
@arikfr
Copy link
Member

arikfr commented Jan 23, 2014

@yosefw shouldn't this be 3 separate "issues"?

@yosefw
Copy link
Author

yosefw commented Feb 3, 2014

I believe an issue is the problem, not the solution :-)

@arikfr
Copy link
Member

arikfr commented Feb 3, 2014

@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
Labels
Projects
None yet
Development

No branches or pull requests

2 participants