Hi, I just round about openfoodfacts, great idea!
I come from a very different area (visual effects), but we too have to deal with big databases with loads of assets from the real world, from tires to grass to water to food to movements to skies, etc.
Its always very tempting to put them in hierarchies, but IMHO, based on my own experience, its almost always better to use tags instead of hierarchies.
So, instead of having to chose which brach a yogurt with orange juice belongs to, just add as many tags as needed, like yogurt, milk, juice, fruit, etc.
And of course a hierarchy can always be derived or inferred from the tags.
Just my two cents.
Hi, I just round about openfoodfacts, great idea!
I come from a very different area (visual effects), but we too have to deal with big databases with loads of assets from the real world, from tires to grass to water to food to movements to skies, etc.
Its always very tempting to put them in hierarchies, but IMHO, based on my own experience, its almost always better to use tags instead of hierarchies.
So, instead of having to chose which brach a yogurt with orange juice belongs to, just add as many tags as needed, like yogurt, milk, juice, fruit, etc.
And of course a hierarchy can always be derived or inferred from the tags.
Just my two cents.