Prepare scrape image storage schema

2026-08-05 23:47:57 +02:00
parent aa138b62ad
commit 05338a062a
3 changed files with 108 additions and 0 deletions
@@ -164,6 +164,9 @@ There are three selectable data sources:
 - The source-candidates popup must provide a `Reload` action beside `Close`; `Reload` bypasses only the current product's cached source result and re-runs the source lookup using the current local mapping configuration. It must not switch database modes or write to Live DB.
 - Source candidates show how they were found, including EAN/reference/name and color context.
 - Each source row has its own `Get pictures` action.
+- Picture candidates must show source, image dimensions and the proposed target assignment. The target assignment is not always color: supported strategies are `color`, `size`, `combination` and `manual`. Start by using manual corrections from the user, then learn reusable rules in Local scrape DB.
+- Scraped pictures and their metadata belong in Local scrape DB, not browser localStorage. Store the binary image in `scrape_image_blobs` with `sha256`, `perceptual_hash`, mime type, dimensions and size. Store each source/target proposal in `scrape_picture_candidates`.
+- Use `sha256` to remove exact duplicate image files and a perceptual hash to flag visually similar images from different sources or sizes. Exact duplicates may be collapsed automatically; visual duplicates should remain reviewable until the user approves the rule.
 - Product source cache is cleared when a new product loads.
 - Hudy picture parsing uses the correct product color variant, checks EANs and extracts large gallery images.
 - Idealo uses the browser adapter and is intended mainly as a picture source.