AEM Assets Admin View language filter returns assets with incorrect metadata language
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article describes why the Language filter in Adobe Experience Manager (AEM) Assets Admin View may return assets whose metadata language does not match the selected filter, and provides steps to filter assets by their actual metadata language.
Description description
Environment
Adobe Experience Manager (AEM) Assets (all versions)
Symptoms
When using the Language filter in the AEM Assets Admin View, assets with a language other than the selected value (for example, ‘en’) appear in the filter results. For example, after selecting the Language filter and entering ‘en’, assets with different language metadata are still shown. This can be confirmed by checking the jcr:content/metadata/dc:language property of assets in the filtered results. No error messages are displayed, but the filter results do not match the expected asset language metadata.
Cause
The built-in Language filter in AEM Assets Admin View filters assets based on the language code present in their folder path (for example, /content/dam/.../en), not the asset’s jcr:content/metadata/dc:language property. As a result, assets whose metadata language differs from the folder path may appear in the results.
Resolution resolution
Follow the steps below to filter assets by their actual metadata language:
- Open the Assets Admin Search Rail in AEM.
- Add a new Property Predicate.
- Set the Property Name to
jcr:content/metadata/dc:language. - Enter the desired language code (for example,
en) as the value. - Apply the filter to view assets with the specified language in their metadata.
For detailed instructions, refer to the Adobe Search facets documentation.