Image Sync Revamp

[dunagan5887]

• A new image_sync queue task object will be created. Each image_sync queue task will transmit 1 image to Reverb
• The image_sync queue task will be on the unique task table. The unique_id will be a concatentation of the sku and the catalog_product_entity_media_gallery table value_id field (the primary key on that table)
• Upon listing creation, an image_sync queue task will be created for each gallery image on the product. No photos will be included in the actual listing creation API call
• Upon the product after_save event, if a new gallery image was created on the product, a new image_sync queue task will be created for that image

[skwp]

as per discussion in chat let's make sure we key off of the unique magento gallery id and use the filename as a column that's not necessarily searchable

[dunagan5887]

"use the filename as a column that's not necessarily searchable"

By this do you mean you won't want to be able to search by filename? By putting the subject_id column onto the database table, we get sorting and filtering on that column for free in the grids

Virtually any column we add to the database table comes with free sorting and filtering. The current issue with not being able to sort/filter is that a number of the columns in that grid come from the serialized arguments object field, which doesn't allow for an immediate implementation of sorting and filtering

[skwp]

search by file name is good to have

Yan Pritzker yanpritzker.com via iPhone

On Sep 24, 2015, at 11:31 PM, Sean Dunagan notifications@github.com wrote:

"use the filename as a column that's not necessarily searchable"

By this do you mean you won't want to be able to search by filename? By putting into the database table, we get sorting and filtering on that column for free in the grids

— Reply to this email directly or view it on GitHub.