Language search filter not functioning in Adobe Experience Manager as a Cloud Service (AEMaaCS)
This article explains the root cause of the issue where the language search filter in Adobe Experience Manager as a Cloud Service (AEMaaCS) doesn’t function as expected when attempting to search for assets by language name and provides steps to fix the search filter to ensure accurate filtering based on asset metadata rather than directory paths.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue
The language search filter in Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets doesn’t return results as expected. Even when assets have language metadata set (For example: “Arabic”), using the language filter in the search doesn’t display those assets. This happens because the filter relies on folder paths with language codes (For example: “ar”) instead of directly querying metadata fields like the full language name.
Steps to reproduce
- Go to the properties of an asset and ensure that the language field is set to a specific language (For example: “Arabic”).
- Navigate to the folder containing the asset:
Assets > Files. - Click on the
Filteroption in the toolbar. - Attempt to search using the
Languagefilter by entering the language name (For example: “Arabic”).
Resolution resolution
- The language filter in AEM as a Cloud Service performs filtering based on directory paths rather than metadata properties. The system recognizes language codes (For example: “ar” for Arabic) in paths but doesn’t recognize full language names (For example: “Arabic”).
- To allow searches by full language names in metadata, customize your search rail by adding a facet that queries against metadata properties instead of directory paths.
By adding this custom facet, the language filter will reference asset metadata fields, enabling more accurate and comprehensive searches across languages based on metadata, rather than location.