ACV acv
Assets Content Validator
Background background
ACV (Assets’ Content Validator) Identifies the missing mandatory nodes and violations in asset content. Such things could lead to failure of certain Assets features on Experience Manager as a Cloud Service.
Subtypes are used to identify the different types of information, such as:
missing.jcrcontent: Identify the folders with missing mandatory nodes in the repository. Identifying any missing content in the repository helps prevent any broken features or use cases.missing.original.rendition: Identify the assets with a missing mandatory original rendition in the repository. Previewing PDF’s pages does not require subassets generation in AEMaaCS. Hence, for PDF assets, reporting subassets missing original rendition is suppressed.metadata.descendants.violation: Identify the assets with more than 100 descendants under metadata node of the asset in the repository.conflict.node: Identify the presence of conflict nodes in the repository under /content/dam/ path.psb.file.large: Identify Large PSB Files (dc:format : application/vnd.3gpp.pic-bw-small) having size greater than 2 GB.invalid.asset.name: Identify assets with invalid characters[* / : [ \ ] | # % { } ? &] in the name.
Possible implications and risks implications-and-risks
- Possibly leads to failure of certain Assets features that depend on inherited properties in Experience Manager as a Cloud Service.
- AEM Assets depends on the existence of the original rendition. The asset processing in Cloud Service goes in a loop if the original rendition is missing. Subassets generation is not supported in AEMaaCS.
- A high number of descendants under a metadata node may slow downloading of folders that contain violating assets.
- The presence of conflict nodes could lead to ingestion failure on AEM as a Cloud Service.
- Experience Manager may not process high-resolution PSB files. Customers using ImageMagick for processing large files might face an impact on the performance if proper benchmarking of the Experience Manager server is not done.
- Invalid characters in the asset name might lead to failures while migrating to AEM as a Cloud Service.
Possible solutions solutions
- Analyze a folder if it has a missing child node. Create the nodes manually if the number of folders is manageable, otherwise use a script.
- For the assets missing the original rendition, either reupload the assets or delete them before migrating.
- No action is required for missing subassets original rendition.
- In there are conflict nodes, they should be resolved or deleted before migrating to AEM as a Cloud Service.
- Contact Adobe Customer Support if you plan to process lots of large PSD or PSB files. Experience Manager may not process high-resolution PSB files that are more than 30000 x 23000 pixels. See documentation.
- Contact the Experience Manager Customer Care Team for clarifications or to address concerns.
recommendation-more-help
c50d24a5-718e-4110-a484-b335e8a63206