Value mappings
Unifying the values of one parameter: "čierna", "black" and "BK" as a single value.
Parameter mapping made sure that
both Barva and Colour end up in the Colour parameter. The other half of
the work is the values. While čierna, Black and BK remain three separate
values, the shop filter offers three "blacks" and the customer picks the one with
two products out of ten.
Controls on this screen
- By parameter — The systematic route: pick a parameter and walk all of its values at once.
- Find a value — The targeted route: search for one spelling across parameters. Right when chasing a single finding.
- Parameter — Until one is chosen the list is empty — that is not a fault.
- Vendor — Narrows the values to one feed. Useful when you know which vendor spells things differently.
- Vendor category — A further narrowing by the feed category.
- Manual category — Narrowing by your own tree — right when normalising one category at a time.
- State — Leaves only mapped or only unmapped values. The unmapped are the queue of work.
- How it works — A summary of the procedure, on the screen itself.
The procedure
Pick a parameter
Start with one the shop filters by — colour, size, material. Parameters nobody filters by are low priority.
Let the AI propose
The AI walks the raw values and proposes which belong together. You confirm.
Finish the rest by hand
Abbreviations and typos the AI could not decipher. The State → unmapped filter is exactly the list of what is left.
The list of values is empty.
No parameter is selected. The screen opens empty on purpose — there are usually far too many values to load them all at once.
When does a mapping show up on products?
On the next import, or immediately after running a re-extraction in Parameter mappings.
I mapped something wrongly. Can it be undone?
Yes, a mapping can be changed or deleted. The original feed values are untouched, so nothing was lost.