Say we create a file (file created by photoshop, illustrator, etc) and upload the file in AEM (All metadata properties are set within the file). 1) User1 downloads the file and edits the file and uploads the file back to the AEM (Since the file Name is not changed, the user now the user uses the create version option, So a version is created to that asset) 2) User2 downloads the same file and updates the asset (this time the user changes the file name as well and uploads the file) The file is uploaded as a new file instead of creating a version. (We don't want a new file to be created, instead we need to create a version)
We need a unique identifier which helps us to identify this is an updated asset of an existing asset in AEM and create a version. We are not looking for Image Set features, this should be incremental feature for images.
AEM understands the file path as a unique identifier, per the requirement the unique ID should be independent of the asset's filename or location in the folder structure.
Has anyone implemented a similar requirement before? If yes, what metadata was taken as the Unique ID and how?
Let's suppose you are using a custom workflow which pulls a metadata value for each file, say some sort of GUID or productID- at the end of the day you are still relying on your end users to set and maintain that metadata, e.g. using the tools built into Photoshop or else Adobe Bridge. So there is a still a chance it won't be done correctly?
If the user is randomly changing the image name, it's better to educate the user or to understand why this is happening. If they rename the file, maybe it is better for SEO purposes?
If the filename is different on the upload, what impact does it have - extra storage required in the DAM? Perhaps the asset can be used again in the future. Or perhaps it muddies the search results? Shouldn't the onus be on the end user to delete unwanted assets.
In short, I am sure there is a technical solution, but would be good to understand if end users role here.