Exclude Assets from AEM Dam Search based on metadata property

Hi ​@RinkiShahi,

You should not try to exclude the asset from the Lucene index itself just because searchable=false.

A cleaner approach is:

1. Add the metadata property to your custom DAM Lucene index so it can be queried:

jcr:content/metadata/searchable

2. Then update the DAM search query/predicate logic to exclude assets where this property is set to false.

For example, if you are using QueryBuilder, add a property predicate like:

property=jcr:content/metadata/searchable
property.operation=unequals
property.value=false

or design the query so only searchable assets are returned:

property=jcr:content/metadata/searchable
property.value=true

The safer enterprise pattern is:

• keep the asset indexed
• make the metadata property indexed/queryable
• filter it at the search/query layer

Trying to conditionally remove assets from damAssetLucene based on metadata can create issues with reindexing, future metadata changes, and other DAM features that still expect the asset to be discoverable.

So the solution is not really “exclude from index”; it is “index the property and exclude it from search results using the query predicate.”

Thanks ​@akhil_merupula for the response, but my use case is to exclude assets from Omni Search (AEM Assets Search UI) entirely if searchable is set to false. I do not have a separate query to run for this.