Live Copy for DAM Assets? | Community
Skip to main content
New Participant
October 16, 2015
Solved

Live Copy for DAM Assets?

  • October 16, 2015
  • 13 replies
  • 3737 views

Hi All,

Is there a feature, similar to "live copy" for DAM assets?  I'm looking for a way to create a parent/child relationship between assets, where the "children" assets inherit from the "parent".  We are currently running AEM 5.6.1, but would be interested in new features that may exist on 6.0 or 6.1 as well.

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ogill

Because of the unique way that AEM stores assets, if you have the exact same file in two locations in the repository, physically only 1 file is stored. The reason being, that each file has a unique SHA1 checksum, the checksum value is used to create a folder/file in the datastore[1]. In this way, you don't duplicate storage for the same file. If the file is modified in any way and uploaded again, only then will a new file in the datastore be created.

However, having a central DAM is always preferable as all instances of an asset will get updated at the same time, otherwise you have to update all nodes that pointed to the original file, which can become inefficient and error prone.

Regards,

Opkar

[1]https://docs.adobe.com/docs/en/cq/5-6-1/core/administering/persistence_managers.html

13 replies

kvanstoneAuthor
New Participant
October 16, 2015

Yes, we do realize it is duplication.  But, would like to have the sites self-contained this way.  

Lokesh_Shivalingaiah
New Participant
October 16, 2015

In that case, it needs to copy/paste or upload again.. I dont think there is a concept of livecopy on assets

ogillAccepted solution
Employee
October 16, 2015

Because of the unique way that AEM stores assets, if you have the exact same file in two locations in the repository, physically only 1 file is stored. The reason being, that each file has a unique SHA1 checksum, the checksum value is used to create a folder/file in the datastore[1]. In this way, you don't duplicate storage for the same file. If the file is modified in any way and uploaded again, only then will a new file in the datastore be created.

However, having a central DAM is always preferable as all instances of an asset will get updated at the same time, otherwise you have to update all nodes that pointed to the original file, which can become inefficient and error prone.

Regards,

Opkar

[1]https://docs.adobe.com/docs/en/cq/5-6-1/core/administering/persistence_managers.html