Product Name Cleanup — Phase 4

This dashboard reviews pd_name_cleanup_staging and writes approved English product titles and specification snippets into oc_product_description. Filter the queue, edit a proposed title or HTML snippet in place, approve unflagged rows, then commit approved batches. A commit reads the live description, removes an existing cleanup block, appends the new snippet between PD_CLEANUP comment markers, and stores the proposed name. Titles longer than 70 characters stay flagged and are not written to the catalog.

Operator Workflow

Work through these five steps in order. You do not need to edit code or open the database.

Technical reference

• Passed Audit is passed_audit. Bucket A (Auto) is auto_processed. Bucket B (AI) is ai_completed. Flagged Review is is_flagged = 1 or a proposed title over 70 characters.
• Filters cover status, bucket, and a keyword matched to product id, original name, or proposed name. Pagination links and the page jump keep those filters.
• The grid loads 50 rows at a time. Choose 25 or 100 on the filter bar. Spec drawers open under the row.
• Changing a proposed title or snippet saves that product and language immediately. The length badge is green at 70 characters or fewer and red above 70.
• Approve sets staging status to approved and does not change the live catalog. Approve Visible Page does that for every unflagged, non-committed row on this page whose proposed title is 1 to 70 characters.
• Commit Approved Batches to Production processes English rows (language_id = 1) with status approved and is_flagged = 0, in batches of 250. Each batch is one database transaction.
• The live description is cleaned with the PD_CLEANUP comment pattern. If that pattern fails, the product is flagged REGEXP_STRIP_FAILURE and skipped. A failed batch rolls back. The browser retries up to 3 times, waiting 3 seconds between tries.
• Original names and descriptions on the staging row are not rewritten here. Every production update binds both product_id and language_id.