The scrape task is not being initialized properly

Today, we are posting items and what the estimated cost is. For the times that we post items that are above the budget, we should factor the budget into it

The estimated cost before tax should be item.price - budget

Problem

Having a strict sub-budget approach can be kinda restricting. Give the ability to ask for recommendations under 1.5x the amount of budget, in increments of a dollar.

For example, if the budget is $8, the recommendations can be up to $12 ($9, 10, 11, 12).

Caveat: Taxes in Fooda vary by restaurant distance. This means that the standard Cook County tax might not always be the case. Some users have reported as much as 15% tax.

This integration keeps breaking and it's annoying. Please write some tests for the app.

Problem

There are people that might not be able to eat all the recommendations we are providing. We need to be able to filter by vegetarian, vegan and gluten-free.

Problem

It would be nice to have some kind of way to leave feedback on items that are available on Fooda.

This could be a slack command, or a website, to leave feedback on an item.

Problem

Now that dietary information is being stored, we should leverage that information to create offerings for folks with dietary concerns.

At the moment, the only dietary concerns we collect are gluten free, vegetarian and vegan.

• Create engine
  • Scope recommendations for gluten-free
  • Scope recommendations for vegetarian
  • Scope recommendations for vegan
• Render recommendations

Use Rails to create an application

Problem

Logging in and extracting data out of fooda is a pain. We should find a way of improving that.

The problem today is that we store every single item ever offered. This is neat for historical purposes.

Since we're on a free-tier of Heroku's postgres, it might be wise to only do a partial update when possible.

Scenario:

1. New item is found, and inserted
2. The same item is found at a later day AT THE SAME PRICE -- only update the date offered + url
3. If the same item is found at a later day with different price, store it

The app is hosted in Heroku, so the free tier of Postgres only supports up to 10k rows. This app currently stores every item ever offered by every restaurant.

We should only store the last delta of the item is offered, that way we can continue to support price deltas. We should have at most two instances of a FoodItem.

Problem

The recommendation engine will sometimes recommend items like "sauces" or a single tortilla, which is pretty unrealistic for a meal, or something that you can share with coworkers.

Screenshots

Proposal

There should be the option to black list some items.