...
So far we've worked with two different approaches for image tagging.
**It's important to note that only the Image Type model training is managed by us. The color model however was created and managed by another company and it's not under our control.
ML Results caching
Most of the advertisers' inventories don't change too much from day to day, so in order to avoid classifying the same images multiple times, we use a cache system in the ML servers.
...
Image Type received from ML system
This value defaults to “Placeholder” if the ML system could not return a value
Color received from ML System
This value defaults to null if the ML system could not return a value
If the color value is configured in the scrape the ML classification for the model is not applied
Image Type Manual fix
Image Type manual fix list selects the value returned from the ML system or defaults to Placeholder if None is received.
Color Manual fix
Color manual fix list selects the value returned from the ML system or defaults to “Black” if None is received
Example of Placeholder tagged from ML system: {Image Type = Placeholder, Color = None}
As you see, as color is not tagged, 5 is not showing anything
Previously tagged Placeholders were {Image Type = Placeholder, Color = 'N/A'}. If you find some of these they of these they are cached values.
Edit
When you change any value from the Manual fixes list and press the “update” button at the bottom of the list the following happens:
...
Different criteria between advertisers that share image CDN
This case didn't happen so far but it is a possibility.
We currently have no images with conflicting classifications but there is potential when advertisers share inventory. When storing the classification of an image we store it by image_key|image_url without linking it to an advertiser. This can lead to the scenario where two advertisers that share CDN are manually reclassifying the images against each other.
...
A request is sent to the ML server to change the image type or color of that image (identified by its image_key).
A historical entry of manual fix is saved in the DB with the data of the reclassification, the advertiser the image belongs to, and who did the fix.
...