Asset Metadata does not transfer during the asset copy

[PovEim]

Hi Team,

I've just discovered that on my 6.5 in-house AEM DAM the metadata of the asset does not transfer if the asset is copied to a different location. 

In the Copy Assets section in this manual:https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/managing/manage-asse... it says that date and date created will not be copied, which I understand.

In my case I have an asset that came with the metadata from original source. I fixed the metadata (Title, Description, Tags, Keywords) on the original file, then needed to copy it to a new folder to have two copies. The new copy of the file is displaying the metadata it came with from the original source. Why did the AEM DAM not transfer the metadata that was added through the UI? Is this a bug? This means that my stakeholders who copied assets from the folder of assets with updated metadata are seeing wrong or non metadata at all. I tried applying different metadata schemas, but it did not make any changes. 

Thanks

[EstebanBustamante]

Hi, 

I was not able to reproduce what you are describing. Perhaps I did something wrong. What I did was update the metadata of an asset (title, description, tags) and then copy it to another folder, all using the UI. The metadata transferred as expected.

Original:

Copy:

As the documentation you shared states, the metadata is transferred to the copy as expected because it is not unique to the asset (https://experienceleague.adobe.com/en/docs/experience-manager-65/content/assets/managing/manage-asse...). What I suspect might be happening in your case is that some metadata is not allowed in the target location. Could you do a simple spot check by copying the image to a new folder outside your typical DAM folder structure and see if it behaves as expected? You can use the wknd folders as I did if you have those assets available to you. 

Note I used AEM 6.5.17.

Hope this helps

[PovEim]

Hi @EstebanBustamante ,

Thank you for getting back to me and running the test on your end! 

I did what you suggested by copying the file from source folder to just outside the main folder structure. The result is unfortunately the same - the metadata reverted to the version the file came with. According to the manual in I supplied earlier, the DAM was meant to create ...-1.jpg file naming to not have duplicate filenames. However that did not happen either. The first from the top is the source that was copied outside the BMS folder. 

Many thanks

[EstebanBustamante]

Hey @PovEim , sorry for the late reply. I suspect that perhaps you have some workflows or other processes happening. Can you please try copying another set of assets completely outside your project folders? For example: Create a new folder under /content/dam called source, and add an image named original.jpg. You should end up with something like /content/dam/source/original.jpg.

Then, update the metadata for original.jpg, create a new folder called destination, and paste the original.jpg file there. Copy the file multiple times (e.g., original.jpg, original1.jpg, etc.) to validate that the assets are being appended correctly, keep in mind the title would remain the same but the "name" of the asset will be updated as shown below.

Let me know if that works. Also, could you confirm which version of AEM you are using?

[PovEim]

Hi @EstebanBustamante ,

Thanks for the instructions! I did as instructed and this is what I observed:

- The Metadata that was added to the file in Adobe Bridge successfully imported into the AEM DAM.

- After the file was ingested, I updated the metadata within AEM.

- I created a Destination folder and copied the file there. The metadata reverted to the Adobe Bridge metadata and the filename did not get *1 at the end.

- Then I copied the same file into the Destination folder again creating the duplicate. Only then the filename received *1 at the end. Metadata reverted back to Adobe Bridge metadata.

- Within the same folder if the metadata is again updated in AEM and a triplicate is created - the metadata reverts to the original. The third file received *2 at the end of the filename.
Please see the attached images.

Conclusion of this exercise - AEM DAM permits same filenames if the files live in different folders within the DAM. It only adds *1 to the end of the filename if the same file is copied in the same folder more than once. This means AEM DAM currently permits same filenames all across the DAM unless they are in the same folder. From my perspective - this should not be like that. 

AEM Version: 6.5.19.0

I am unable to attach more than three images to this threat unfortunately... I tried combining the images for demo purposes. 

Many thanks