You're viewing help content for version:
- 6.4
- 6.3
- 6.2
- Older Versions
Use Search Facets to add search predicates to the Search panel in Adobe Experience Manager (AEM) Assets or modify existing search predicates. Search predicates lets you customize your search based and makes the search functionality versatile.
You can add multiple predicates to the Search panel. For example, add the Fulltext predicate for full-text searches. Use the Property predicate to search for assets that match a single property that you specify. Use the Options predicate to search assets that match one or more values that you specify for a particular property. Add the Date Range property to search assets created within a specified date range.
-
In the Property Name field, enter a name for the property based on which the search is performed. For example, enter jcr:content/metadata/dc:description or ./jcr:content/metadata/dc:description.
Note:
Ensure that the Property Name field and other required fields are not empty and that they contain valid values. You cannot submit the Search form without specifying valid values for required fields.
The Options predicate is the most versatile of predicates. It lets you configure multiple search options in the Search panel.
Once configured, you can select one or more of these options in the Search panel to search for assets based on them. For example, to provide the ability to search for assets based on file type in the Search panel, configure options, such as Images, Multimedia, Documents, and Archives in the Search form. After you configure these options, the search is performed on assets of type gif, jpeg, png, and so on when you select the Images option in the Search panel.
To map the options to the respective property, create a node structure for the options and provide the path of the parent node in the path property of Options predicate. The parent node should be of type sling:OrderedFolder. The options should be of type nt:unstructured. The option nodes should have the properties jcr:title and value configured.
The jcr:title property is a user-friendly name for the option that is displayed on the Search panel. The value field is used in the query to match the specified property.
When you select an option, the search is performed based on the value property of the option node and its child nodes, if any. The entire tree under the option node is traversed and the value property of each child node is combined using an OR operation to form the search query.
For example, if you select "Images" for file types, the search query for the assets is built by combining the value property using an OR operation. For example, the search query for images is built by combining the results matched for image/jpeg, image/gif, image/png, image/pjpeg, and image/tiff for the property jcr:content/metadata/dc:format using an OR operation.
Instead of manually creating a node structure for the options in the CRX repository, you can define the options in a JSON file by specifying corresponding key-value pairs. Specify the path of the JSON file in the JSON Path field. For example, you can define the key-value pairs, image/bmp, image/gif, image/jpeg, and image/png and specify their values as shown in the following sample JSON file. In the JSON Path field, you can specify the CRX path for this file.
{
"options" :
[
{"value" : "image/bmp","text" : "BMP"},
{"value" : "image/gif","text" : "GIF"},
{"value" : "image/jpeg","text" : "JPEG"},
{"value" : "image/png","text" : "PNG"}
]
}
Note:
The Options predicate is a custom wrapper that comprises property predicates to demonstrate the described behavior. Currently, there is no REST endpoint available to support the functionality natively.
-
In the Settings tab, enter a label and a name for the property. For example, to search assets based on their format, specify a user-friendly name for the label, for example File Type. Specify the property based on which the search is to be performed in the property field, for example jcr:content/metadata/dc:format.
Caution:
Both step 5 (Configuring the JSON path) and step 6 (Configuring the Options path) describe alternative ways to configure options for the Options predicate. Therefore, perform either step 5 of step 6 (not both simultaneously) and then proceed with the subsequent steps in this procedure.
Similar to the way you add a Property predicate or an Options predicate, you can add the following additional predicates to the Search panel:
Predicate Name |
Description |
Properties |
Fulltext |
Search predicate to perform full text search on an entire asset node. It is mapped with the jcr:contains operator. You can specify a relative path if you want to perform a full text search on a specific part of the asset node. |
|
| Path Browser | Search predicate to search for asssets in folders and subfolders at a preconfigured root path |
|
Tag |
Search predicate to search assets based on tags. Configure the Options Path property of this predicate to populate various tags in the Tags list. Set this property to a node that contains various tags as child nodes. |
|
Path |
Use it to filter results on location. You can specify different paths as options. |
|
Publish Status |
Search predicate to search assets based on their publish status |
|
Relative Date |
Search predicate to search assets based on the relative date of their creation. For example, you can configure options, such as 2 months ago, 3 weeks ago, and so on. |
|
Range |
Search predicate to search assets that lie within a specified range. In the Search panel, you can specify minimum and maximum values for the range. |
|
Date Range |
Search predicate to search assets created within a specified range for a date property. In the Search panel, you can specify Start and End dates using date pickers. |
|
Date |
Search predicate for a slider-based search of assets based on a date property. |
|
File Size |
Search predicate to search assets based on their size. It is a silder-based predicate where you select the slider options from a configurable node. The default options are defined at /libs/dam/options/predicates/filesize in the CRX repository. File size is provided in bytes. |
|
| Asset Last Modified | Search predicate to search recently modified assets |
|
| Publish Status | Search predicate to search for assets based on their publish status |
|
| Rating | Search predicate to search assets based on their average rating |
|
| Expiry Status | Search predicate to search for assets based on their expiration status |
|
| Hidden | Search predicate that defines a hidden field property to search for assets |
|
The Lock icon disappears if you add search facets to the form indicating that the default form has been modified.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.