Sonia,
Assuming that when a new image has the same URL, you are talking about the new image being a replacement for the old image, then I think your best bed would be to have the workflow process download the file (unless there's a way to get just the metadata, including the file size for the image using the URL) and compare the image size with the one in the DAM. If the file sizes are the same, then it could be assumed that the image hasn't changed (this assumes that most updates would result in a different file size). The alternative would be if there was any metadata that can be retrieved for the image without having to actually download the image - if this metadata isn't already stored in the DAMMaster record (or the repository that stores the details for these assets), then the necessary fields could be added. You'd need to pre-seed them for the images you already have, but then you could have your workflow process pull the current metadata down and compare it to the previous - if there are differences that indicate an image change, then the process can proceed with actually downloading the file and submitting it to the DAM for processing.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
------------------------------
Original Message:
Sent: 04-14-2021 11:45
From: Sonia Singh
Subject: Images
Brian, there is a EPX workflow that is triggered by the scheduled export in the PIM UI. The workflow queries the PIM DB Prestaging Source Item Asset repository for new/updated records since the last run & downloads the assets in the temp folder on the EW server. Please let me know if you need more details. Thanks.
------------------------------
Sonia Singh | Product Owner
Dot Foods | (630) 686-3780
Original Message:
Sent: 04-13-2021 05:22
From: Brian Zupke
Subject: Images
Sonia,
What is the process that picks up the file from the URL defined in the XML? Depending upon how this is being done, one option might be to get the size of the file downloaded from the URL and compare it to the size of the record in the DAM. If they are the same, then it would be fairly safe to assume the asset content has not changed. But if the sizes are different, the asset would need to be re-submitted to the DAM.
-Brian
------------------------------
Brian Zupke | Senior Technical Support Engineer
Winshuttle North America | 9099009179
Original Message:
Sent: 04-07-2021 09:27
From: Sonia Singh
Subject: Images
We have an asset repository which stores the Asset URL, file name & the source GTIN received from the GDSN in an XML format. The XML file contains all the data related to an item. Then the Enterworks process picks the URL, downloads the file in the DAM Drop folder. The challenge we are facing is the image record gets updated even though the changes on the XML are related to the item & not image and that results in Enterworks reprocessing the images & longer processing times.
The other idea was to check if the URL changed and only process changed URLs. However, this doesn't work either because new images can have the same URL as a previous image. We discussed looking into the image metadata, but Enterworks doesn't know that information until after the images are processed.
Has someone ran into similar situation or has some suggestion?
Thanks,
------------------------------
Sonia Singh | Product Owner
Dot Foods | (630) 686-3780
------------------------------