manage-ingredient-hierarchy

You can enrich YAML recipes by importing canonical parent-child structures, variant types, and functional roles from MediaIngredientMech to populate fields like parent_ingredient, variant_type, and role for semantic querying and graph readiness.

Ingredient hierarchy drift occurs when recipe data loses consistent parent-child linkages and variant types. Prevent it by importing a canonical ingredient taxonomy from MediaIngredientMech to ensure hydrated or salt variants remain searchable and structurally validated.

You can validate ingredient ontologies by running structural checks that enforce referential integrity, detecting orphaned or circular parent references, verifying valid enums, and generating coverage statistics with Markdown reports.

Yes, you can perform a dry-run hierarchy import by pointing the workflow to a local MediaIngredientMech checkout and a CultureMech YAML directory, limiting processing to a small sample for verification before full enrichment.

You can match culture media ingredients using deterministic index-based matching by CHEBI, name, or MIM identifiers to ensure accurate mapping of parent ingredients and functional roles across bacterial, algae, fungal, and specialized media datasets.

Bulk recipe YAML enrichment requires schema-compatible field additions and referential integrity checks to prevent orphaned or circular parent references, meaning unmatched ingredients without valid CHEBI, name, or MIM identifiers will be skipped during processing.