6 ms·
This is neat. I developed something similar, but specifically for keto recipes: https://ketohub.io https://ketohub.io How are you parsing the ingredients? I w
by mtlynch 7y ago
This is neat. I developed something similar, but specifically for keto recipes:
https://ketohub.io https://ketohub.io
How are you parsing the ingredients? I went deep into the rabbit hole on that part and ended up spinning off a separate ingredient parsing SaaS:
https://zestfuldata.com https://zestfuldata.com
I wrote about the experience last year:
https://mtlynch.io/shipping-too-late/ https://mtlynch.io/shipping-too-late/
- jka 7y agoAwesome, hello mtlynch :) It's great that you found this post; as it happens I'm using your fork of nytimes/ingredient-phrase-tagger (thanks a lot for updating and containerizing it!) in combination with 'ingreedypy' for ingredient parsing. How's zestful doing? It looks great and I did consider using it; the quantity of parsing I was doing led me to choose the container version just to keep my own operational costs down (albeit at the loss of any model retraining you've done).
- mtlynch 7y agoOh, cool! I'm glad it was helpful. Zestful's doing okay. It's in maintenance mode at the moment, but when I have spare time, I like to tinker with it to bump up the accuracy. Customers seem to mostly use it in big bursts, so it'll be a few thousand requests one month, then the next month, it'll drop to only a few dozen. If you ever have patches you want to push back upstream to the open source tagger, I'm happy to review. And if you ever want to do a bulk parse of ingredients on Zestful, I can certainly offer volume discounts.