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.

Sign up for GitHub

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

Jump to bottom

Searching is lame #2

Open
willwashburn opened this issue Dec 6, 2015 · 2 comments
Open

Searching is lame #2

willwashburn opened this issue Dec 6, 2015 · 2 comments
Assignees
@khaliqgant
Labels
enhancement
Milestone
Version 0.0.2

Comments

@willwashburn
Copy link
Member

When you search for a station by name, you have to be really exact. "Broadway and 29th" works but "29th and Broadway" does not.

Also, if the voice cuts off and Alexa only gets the phrase " and 29th" she'll search for that and find the first result with 29 in it.

The only solution I can think of is to brute force it and create a list of "acceptable names" to "station ids" map to search before we query for the number of bikes. Might help with #1 too.
@willwashburn willwashburn added this to the Version 0.0.2 milestone Dec 6, 2015
@khaliqgant
Copy link
Member

A "did you mean" would be be a nice feature / partial solution here.

@willwashburn
Copy link
Member Author

How would we know if it's partial or not?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@khaliqgant khaliqgant

Labels
enhancement
Projects
None yet
Milestone
Version 0.0.2
Development

No branches or pull requests
2 participants
@willwashburn @khaliqgant