OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface.
Use-case:
OOTB Option to search using tag in AEM Assets view for convenient filtering of assets within the AEM authoring interface.
Current/Experienced Behavior:
Currently, tags can be added to any asset but searching for assets with a specific tag is difficult from the native UI. One has to generate a query and use custom reports to get this information.
Improved/Expected Behavior:
There should be an option in AEM Filters to search assets using a tag picker. This feature exists for auto generated tags like Orientation and Style but not for custom tags. PFA.
Environment Details (AEM version/service pack, any other specifics if applicable):
This has been reported to the engineering under the internal reference ASSETS-30293. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Hi @rampai, there are already options available for this. In the admin asset search rail, you can add option predicates that are related to custom tag options of your choice. You can also add additional tag filter predicates and limit the root path of those.
My explanation was more on point than this explanation video. I try again. In the assets-admin-search-rail, you can add additional predicates. There are different predicates that behave differently. What you shown in the screenshot for Orientation, is a tag predicate that has his root path on /content/cq:tags/properties/orientation So the user can only pick tags in this search field that has a tag in this tag structure. If you want to use something similar for your own tag structure property, you can add an additional tag predicate, and set the root path to /content/cq:tags/your-custom-namespace/your-custom-tag/ But you can also use something different than the tag predicate. In my screenshot, the option predicate. Here you give a property name, which can be any custom metadata or what you were looking for, a tag. In this case - add a option predicate, - set the property /content/cq:tags/ and add your options manually by adding names and values. e.g. your-custom-namespace:tag-level-1/tag-level-2/option-1 your-custom-namespace:tag-level-1/tag-level-2/option-2 your-custom-namespace:tag-level-1/tag-level-2/option-3 This will then be a checkbox selector for the user.