Is your feature request related to a problem? Please describe.
The knowledge graph currently categorizes many stocks and vinegars as sub-types of the ingredients they are derived from.
For example, 'red wine vinegar' is considered to be a kind of 'red wine', and 'chicken stock' is classified as a type of chicken ingredient.
These cases imply a need to support byproducts in the knowledge graph: ingredients that are derived from other ingredients (and so may contain the original ingredient in their name) but belong to their own separate hierarchies.
Describe the solution you'd like
It would be useful to create a file that contains a set of mappings from ingredient-related terms to the name of their root byproduct hierarchy.
Is your feature request related to a problem? Please describe. The knowledge graph currently categorizes many stocks and vinegars as sub-types of the ingredients they are derived from.
For example, 'red wine vinegar' is considered to be a kind of 'red wine', and 'chicken stock' is classified as a type of chicken ingredient.
These cases imply a need to support
byproducts
in the knowledge graph: ingredients that are derived from other ingredients (and so may contain the original ingredient in their name) but belong to their own separate hierarchies.Describe the solution you'd like It would be useful to create a file that contains a set of mappings from ingredient-related terms to the name of their root byproduct hierarchy.
For example:
This would be an oversimplification of reality but would enable incremental improvement to the recipe search experience.
Resolves https://github.com/openculinary/api/issues/41