Get smarter about capturing resto data

[farmcp]

• don't just use facebook to search for restaurants. if we have a better restaurant in the database we should choose that over facebook => better is defined by picture, address, phone number, etc
• we should check what restos have the best picture, information, detail on facebook and filter them
• also if we have data for a resto that is being searched we should use that instead

[farmcp]

@hc5duke I think you'd be better than me at this problem - when you get a chance

[hc5duke]

i dont understand this one. we already check our db on save.

[farmcp]

basically when we search for a place on the autocomplete we don't pre-filter restaurants. We get a whole list of places from facebook that aren't really helpful. It'd be better if we just returned things that are in our database first - that way we aren't duplicating facebook. i think in general we just need to be smarter about getting better data.

[farmcp]

maybe we should be merging the restaurants?

[hc5duke]

merge fb with regular? except for the few yelp ones all restaurants already have facebook linked

[farmcp]

I mean ideally if there is a way to merge our information that our users give us with the multiple facebook places that are searched for that would be ideal i think. We would basically solve data integrity issues. Also that would allow us to check our database and return one restaurant if it already existed instead of the 10s of places that fb returns currently.

[farmcp]

Closing this issue as I foudn a better way to filter from facebook. Will want to revisit once we allow users to create restos directly onto bitelist.