Skip to content
knownframe
CookDex docs
Star23
You're reading the docs for CookDex v2026.9.1, an earlier release. See this page in the latest docs.

Data maintenance pipeline

data-maintenance runs CookDex’s cleanup and audit stages in a fixed order:

dedup -> junk -> names -> parse -> foods -> units -> labels -> tools -> taxonomy -> categorize -> cookbooks -> yield -> quality -> audit

Each stage and option is listed under data-maintenance in the task reference. Run the full pipeline for broad maintenance, or select individual stages when you only need a targeted operation.

Section titled “Recommended flow”
  1. Open CookDex at /cookdex.
  2. Go to Tasks and select Data Maintenance Pipeline.
  3. Leave Preview Run enabled.
  4. Choose specific stages only if you want a targeted run.
  5. Run the task and review the log.
  6. For live cleanup stages, switch to Run Live, enable Apply Cleanup Writes, and confirm the owner policy unlock.

Stages

Section titled “Stages”
Stage Purpose
dedup Finds recipes imported from the same source URL.
junk Detects non-recipe pages such as listicles, how-to posts, digests, placeholders, and bad scrapes.
names Normalizes names derived from URL slugs.
parse Parses raw ingredient lines into structured fields.
foods, units Merges duplicate foods and units.
labels, tools Syncs managed labels and tools.
taxonomy Syncs managed categories and tags.
categorize Applies rule-based organization and optional AI categorization.
cookbooks Syncs cookbook rules.
yield Normalizes yield and servings fields.
quality Scores recipe completeness.
audit Audits taxonomy usage and duplicates.

Scheduling

Section titled “Scheduling”

Create an interval schedule in the web UI for recurring maintenance. Use a once schedule for a one-time future run. For routine monitoring, schedule data-maintenance with Preview Run enabled or schedule health-check for a read-only report. See Scheduling.