Show HN: An API for scraping recipe web pages

Post by enobrev » Tue, Jul 18, 2017, 11:13 AM UTC

mosselman wrote: post #38

patrickdavey wrote: post #28

Earlier quoted context omitted.

Heh, I once tried to make a DSL to cope with recipes from cookingforengineers.com e.g. their lovely recipe cards [1] . I totally failed to make anything decent!. The combining of multiple steps etc. was just painful!. In the linked site above, that recipe is so straight forward, I'd love to see how it copes with [1] below. [1] http://www.cookingforengineers.com/recipe/127/Shepherds-Pie-...

Those cards are genius. They perfectly illustrate what you can do parallel to other things rather than having to re-read and re-interpret the written instructions continuously.

Post by Ashleigh44 » Tue, Jul 18, 2017, 11:19 AM UTC

svnv wrote: post #32

askvictor wrote: post #23

Earlier quoted context omitted.

Two things that would be so nice would be easy scaling, and unit conversion (even better if that's automatic)

I created http://www.recipastely.com/ to simplify recipe conversion between us and iso units a few years back. It's not perfect but it seems to work fine for me.

Post by arthurpaul » Tue, Jul 18, 2017, 11:24 AM UTC

Freak_NL wrote: post #6

oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

Whenever I read a recipe online I get this nagging feeling that there should be some widely used open standard for describing recipes that can do all sorts of awesome stuff (like a web crawler such as DuckDuckGo being able to answer "I have a pineapple, cream, and the usual pantry basics, what can I cook?"), but this seems to go directly against the business models of the big recipe sites, so it will not likely see m…

Post by staticelf » Tue, Jul 18, 2017, 11:36 AM UTC

Post by cronin101 » Tue, Jul 18, 2017, 11:44 AM UTC

oneeyedpigeon wrote: post #4

This really seems to be an exercise in 'structuring recipe data' rather than the ins-and-outs of scraping. Seems like a much-needed task; is there anything approaching a 'standard' for recipe data already? "ingredients": [ "600g pineapple, peeled, chopped" ] This seems like a prime candidate for improvement; something like the following would seem to be more useful: "ingredients": [{ "ingredient": "pineapple", "quant…

    ingredients = [
      '200g of heavily salted butter',
      'six bottles of beer',
      '50ml of clotted cream',
      'plain brown flour',
      '1 oz french cheese',
      '8 large eggs',
      '2kg of salted pork',
      'a pinch of salt',
      'a tablespoon of honey'
    ]
    
    ingredients.map { |i| IngredientParser.parse i }
    
    # => ["butter",
    #     "beer",
    #     "clotted cream",
    #     "flour",
    #     "cheese",
    #     "egg",
    #     "pork",
    #     "salt",
    #     "honey"]

    require '../environment.rb'
    require '../scrapers/bbc_good_food_scraper.rb'

    recipe = Recipe.create source_uri: 'http://www.bbcgoodfood.com/recipes/vietnamese-caramel-trout'

    recipe.update_using_scraper BBCGoodFoodScraper

    puts recipe.title

    puts recipe.description

    puts recipe.ingredient_ids.inspect



    recipe.ingredient_ids.each { |i| puts((Ingredient.find i).inspect) }



    =begin

    Vietnamese caramel trout

    A caramel base balances out the hot and salty ingredients of this Asian-inspired one-pan fish dish for two

    [56, 57, 58, 59, 60, 61, 62, 63, 64]

    #
    #
    #
    #
    #
    #
    #
    #
    #
    =end