Subversion Repositories SmartDukaan

Last modification

• Rev 37331 2026-08-18 00:19:29
• Author: amit

• Log message:

  Add offer circular review and curation screen
  
  Shows the nine verbatim PDF columns beside what the parser made of them, uploads a
  new monthly circular, and resolves the products the matcher could not.
  
  Upload deliberately does not parse - it stores the PDF, sha256-deduped, and
  registers it DRAFT, so an upload can never half-populate the offer tables. The cron
  ingest job picks it up from there.
  
  The curation queue groups by distinct (division, raw text) because that is the
  product_alias key: one answer clears every row carrying that text, on this circular
  and on every later one. On the Aug'26 circular that turns 152 unresolved rows into
  106 decisions. Three actions mirror product_alias.action - PIN to a catalog id,
  REWRITE to the catalog's spelling and match again, or IGNORE.
  
  - Writes product_alias only, so nothing the screen does can set manually_curated
  and lock a circular against re-ingest. Coverage decisions, which do need that,
  are listed but visibly parked rather than offered a naming answer.
  - A saved decision changes nothing until re-ingest, because aliases are read at
  ingest time; the queue says so and the re-ingest button puts the document back
  to DRAFT for the scheduler. The portal cannot run the ingest itself - that lives
  in profitmandi-cron, which fofo does not depend on.
  - The closest rejected match is shown for context and never pre-selected. Four new
  OnePlus models each "nearly" matched a 2015 OnePlus 2 at 0.80-0.84, and offering
  that as a suggestion invites a reviewer to confirm it. Where the catalog has no
  such SKU the search says so and steers to IGNORE.
  - aliasExport emits every decision as replayable SQL, because the portal writes to
  one database and environments would otherwise drift apart silently.
  
  Access is an email allowlist AND the admin role. Both are enforced in the
  controller; the sidebar entry repeats the allowlist because visibility in auth.menu
  is role-driven and cannot express a per-email rule.
  
  No jsVersion bump: offer-circular-review.js is a new file that was never cached,
  so it needs no cache-buster, and churning that shared counter only conflicts with
  whoever is mid-edit on it.