You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently there is no distinction in the knowledge graph between ingredient products (e.g. sesame seeds) and ingredient categories (e.g. seeds) -- both are treated as potential recipe ingredients.
This can cause a problem because currently a line of ingredient text (e.g. sprinkle of sesame seeds) can be matched against the product name seeds -- and seeds isn't an appropriate ingredient to display (because not all seeds are valid substitutes, and consumers generally won't find products labeled simply as seeds).
Describe the solution you'd like
Make a distinction between ingredient categories and products. This could be implemented as a simple flag on the existing products entries, or by creating a new model/entity type for categories.
Describe alternatives you've considered
N/A
Additional context
The need for a feature to resolve this problem was noted during development of our response to our first UK Online Safety Act risk assessment.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently there is no distinction in the knowledge graph between ingredient products (e.g.
sesame seeds
) and ingredient categories (e.g.seeds
) -- both are treated as potential recipe ingredients.This can cause a problem because currently a line of ingredient text (e.g.
sprinkle of sesame seeds
) can be matched against the product nameseeds
-- andseeds
isn't an appropriate ingredient to display (because not all seeds are valid substitutes, and consumers generally won't find products labeled simply asseeds
).Describe the solution you'd like
Make a distinction between ingredient categories and products. This could be implemented as a simple flag on the existing
products
entries, or by creating a new model/entity type for categories.Describe alternatives you've considered
N/A
Additional context
The need for a feature to resolve this problem was noted during development of our response to our first UK Online Safety Act risk assessment.
The text was updated successfully, but these errors were encountered: