Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Sub-Assets and Reference Dependencies

Avatar

Level 1

This has been an ongoing question for our DAM Admins and Librarians.

Occasionally our Librarians do not have the option to publish an asset from the DAM due to a sub-asset (an image used in this asset) having been expired.

This image asset was previously ingested to the DAM, and used in an older asset and is now expired.

 

So a totally new asset was created and ingested to the DAM, and it used a copy of the same image asset that was already in the DAM, with a different file name.

 

Here is the new asset to be published with the Status in Red showing "Sub-Asset":

Asset to be Published and Status.png

Once you navigate to the asset's metadata Properties you see the list of References, and the second red-flagged item represents the same image used in the new asset to be published:

Asset Metadata with References and Dependencies.png

 

I would like to understand more about Sub-assets and References to these sub-assets in order to avoid this issue in the future.

Does this have anything to do with the way that a Creative might re-use an image asset from the DAM in another, totally new asset?

Thanks in advance for any assistance.

 

Mark W. Holmes

Herbalife Nutrition

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Sub-asset generation can be very resource intensive on any Experience Manager deployment. If you are generating sub-assets when complex assets are uploaded, add the DAM Update Asset workflow step. If you are generating sub-assets on-demand, you can create a separate workflow to generate sub-assets. A dedicated workflow allows you to skip the other DAM Update Asset workflow steps and save computational resources.

Reference: https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/managing-linked-subass...

 

Also, you can refer https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-21206.html%3Flang%3Den and https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/drm.html?lang=en#ass... for Sub-Assets.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Sub-asset generation can be very resource intensive on any Experience Manager deployment. If you are generating sub-assets when complex assets are uploaded, add the DAM Update Asset workflow step. If you are generating sub-assets on-demand, you can create a separate workflow to generate sub-assets. A dedicated workflow allows you to skip the other DAM Update Asset workflow steps and save computational resources.

Reference: https://experienceleague.adobe.com/docs/experience-manager-65/assets/managing/managing-linked-subass...

 

Also, you can refer https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-21206.html%3Flang%3Den and https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/drm.html?lang=en#ass... for Sub-Assets.