Custom Search Form for DAM content path | Community
Skip to main content
R
Rob_Curran__T4G
Level 3
June 22, 2016
Solved

Custom Search Form for DAM content path

  • June 22, 2016
  • 3 replies
  • 2627 views

When you customize the "Assets Admin Search Rail" search forum the changes you make (adding predicates for example) are visible in all contexts in Assets.

https://docs.adobe.com/docs/en/aem/6-2/administer/operations/search-forms.html

Is there any way to have the custom predicates only show for specific paths in the content tree?  Eg. not visible in /content/dam/abc but visible in /content/dam/def

Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by amitgupta_adbe

>especially in multi-tenant scenarios where different groups with vastly different metadata share a common DAM repo

For a multi-tenant scenario, instead of doing this at filter level. You would create different schemas for each tenant or path. Then customize the UI to pick up, those different schemas. 

3 replies

G
Adobe Employee
gaujainAdobe Employee
Adobe Employee
June 23, 2016

Metadata Schemas can be applied per folder but Search facets not. You can review how it is being done for metadata schemas and replicate that accordingly.

Thanks.

R
Rob_Curran__T4GAuthor
Level 3
June 23, 2016

Thanks for the response / confirmation.

Is the implementation for Metadata Schemas something you are familiar with?  Just wondering if you can save me some reverse engineering... what components / code should I be looking at to implement this custom functionality?

Any idea on level of effort?

We had already configured the custom metadata schema for our specific folder in the DAM.

Seems like something that should be available OOTB, especially in multi-tenant scenarios where different groups with vastly different metadata share a common DAM repo.  But then they have to sift through everyone elses metadata values in the filter.

amitgupta_adbe
Adobe Employee
amitgupta_adbeAdobe EmployeeAccepted solution
Adobe Employee
July 11, 2016

>especially in multi-tenant scenarios where different groups with vastly different metadata share a common DAM repo

For a multi-tenant scenario, instead of doing this at filter level. You would create different schemas for each tenant or path. Then customize the UI to pick up, those different schemas. 

Terms & ConditionsAccessibility statement

Loading footer...