Link a AEM Asset Folder to another Folder to avoid Duplicate content/image | Community
Skip to main content
Level 2
August 23, 2024
Solved

Link a AEM Asset Folder to another Folder to avoid Duplicate content/image

  • August 23, 2024
  • 3 replies
  • 808 views

Hi All,

I have a folder structure a shown below

 

/Content/dam

/content/dam/Common

/Content/dam/FolderA/Common

/Content/dam/FolderB/Common

 

I dont want duplicate the content/images of Common DAM folder under Folder A and Folder B

 

I tried creating a nt:/linkedfile and jcr:Reference etc... but nothing worked.Is there any solution to link one folder to another folder in AEM DAM.Please suggest

 

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 EstebanBustamante

Sorry, I don’t understand the issue. If the assets are "common," meaning they are shared among other folders, you should place them in a common folder rather than in specific folders like FolderA and FolderB. What would be the purpose of /FolderA/Common? I think you need to reconsider the taxonomy and how to approach your business use case. My advice would be to maintain a separate folder for "shared" assets and not include those assets in the specific ones. You can check how the Wknd.site structures their assets as an example.

 

Hope this helps.

3 replies

Level 2
August 26, 2024

Any thoughts on this @arunpatidar

Adobe Employee
August 27, 2024

@rajashankar33: May be you can use asset  collection if that works for your use case which only keeps reference. Or make use of metadata - like tags or drop down values to indicate the usage of assets .

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
August 28, 2024

Sorry, I don’t understand the issue. If the assets are "common," meaning they are shared among other folders, you should place them in a common folder rather than in specific folders like FolderA and FolderB. What would be the purpose of /FolderA/Common? I think you need to reconsider the taxonomy and how to approach your business use case. My advice would be to maintain a separate folder for "shared" assets and not include those assets in the specific ones. You can check how the Wknd.site structures their assets as an example.

 

Hope this helps.

Esteban Bustamante