SUB-ASSET status displayed for Asset

Description description

Environment

  • Experience Manager
  • Experience Manager 6.5

Issue/Symptoms
While browsing the asset, some assets show a “SUB-ASSET” status:

What does this mean?

Resolution resolution

The SUB-ASSET status does correspond to when your asset has some related assets for which their Digital Rights Management date expired.

This is a specific case of the scenario where the main asset itself expired, documented here:

https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/drm.html?lang=en#asset-expiration

You can check which related asset is expired by opening the asset’s properties Basic  tab and observing the red flag  icon:

The related assets in question are of two kinds:

#1 - Asset is a PDF with sub-pages

If you have modified your “DAM Update Asset” to extract pages from your PDF, then it will create a sub-asset for the document pages.

Each extracted page is an asset, stored under the main asset, in a sub-node/folder named “/subassets” and does have metadata properties, including the DRM Expires date in the Advanced tab.

If that Expires  date has passed, you will see:

  • the EXPIRED status for this sub-page/asset when browsing the main PDF subassets (using the top left rail, switch from Content Only view to Subassets)
  • the SUB-ASSET status when moving back to the main PDF

This is documented on the following page 0.

#2 - Asset has references assets

For any type of asset, it is possible to make reference to other assets. The SUB-ASSET  status is also computed by looking at the Expires  date of each of these references.

Those references are stored in a property:

asset/jcr:content/related/links/sling:members/sling:resources

Note:

In the case your asset does have too many references (several thousand), then it might cause some UI performance issues when trying to display the asset properties.

Checking/computing the status of all those references might take too much time, and the request to open the properties will time out.

Having too many references is concerning and needs to be investigated, as it can cause performance issues:

https://jackrabbit.apache.org/oak/docs/dos_and_donts.html#Large_Multi_Value_Property

To fix the issue, if these related references don’t bring any value, one can delete the following folder/subnode from CRX/DE:

/conten t/.../asset/jcr:content/related/links

****#3 - Tips for checking expired assetsYou can use the following JCR SQL2 query to list all assets in your repository that has an expiry date reached:SELECT * FROM dam:Asset WHERE jcr:content/metadata/prism:expirationDate cast('2023-01-02T17:00:00.000Z' as date)Change the date to the current time (in GMT format).

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f