Why are there so many problems with product information that is already in the database.

amarkula wrote: »

Use case:
I scan in an EAN-code for turkey slice and input 9 grams.
Result I get is 3,766kJ (about 900kcal) and that it includes distribution of 18/35.1/126 grams of nutritions.

Probably before you read this line, you already know where's the problem, so why are all these in the database?

Bad data in, bad data out and bad data can't be turned into gems.
Or if contributions are encouraged over exactness, there should be a way to resolve all items that break the laws of nature, maybe just let them expire very quickly, as no one will get the benefit for 126grams of protein from 9 grams of turkey.

My vote would go into exact values over other values, but that may be because of my background.

And while I write this, How do I copy community contributed entry to my foods and add (correct) serving size to it?

The solution is to check the entries the first time you use them, and make sure they're right. The database is crowd-sourced, which means it's very extensive (which is good), but also that it contains inaccurate entries (either from careless users, or in some cases products that have changed formulations since first being entered, or because formulations of the same-named product differ between countries. Scanning doesn't get you better (more accurate) entries, it just gets you entries some user linked to the bar code. For most foods/products, there's an accurate entry in the database. If not, correct the one that's there, or add it yourself.

When you look up a food in the database, and log it in your day, it will get added to your "frequent/recent foods", and default to the quantity you last used. Next time you do a search (in the app), your frequent/recent entry will come up first, and you can accept the quantity or change it, whichever suits you. (In the web browser version of MFP, as opposed to the app, the food search works a little differently, but you still have an easy option to rely on your own recent/frequent foods.)

This all sounds kind of weird, I know, and there's extra checking when you first start that seems time-consuming, but as you get more recent/frequent foods, own saved recipes, own saved meals, it just keeps getting quicker and easier.

Hang in there.

There is a simple solution. All MFP has to do is drop the ones people don't use. Over time all the bad ones will be gone. But, they are too stupid or too cheap to perform this obvious fix.