AEM Assets - Filter search should only return matching assets | Community
Skip to main content
A
arctouch-emanuelmachado
New Participant
November 2, 2021
Need info

AEM Assets - Filter search should only return matching assets

  • November 2, 2021
  • 2 replies
  • 1164 views
Request for Feature Enhancement (RFE) Summary: AEM Assets - When using the Filter rail to search, it should only display matching assets. 
Use-case: Using the Filter rail, with a Property Predicate set up, adding a keyword to that field should make it so the filter only returns assets that have that value in the configured metadata field.
Current/Experienced Behavior: Search returns all assets that contain said keyword in any metadata property
Improved/Expected Behavior: Search returns all assets that contain said keyword in the metadata property configured in the Property Predicate
Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Service Pack 8
Customer-name/Organization name: The Raymond Corporation
Screenshot (if applicable):

 
Code package (if applicable): N/A
Notes: This feels like a bug to me, and certainly not a "new idea", but we opened Support Ticket E-000488914 and were told to file a "feature enhancement request".

2 replies

A
arctouch-emanuelmachadoAuthor
New Participant
January 18, 2022

Hi @akash_kapoor ,

 

Sure thing! Currently, on our AEM 6.5.8.0 instance, we have created a Filter Predicate with this configuration:
Type: Property Predicate

Field Label: MILS Product Family

Placeholder: data cleanup

Property Name: jcr:content/metadata/trcmilsProductFamily

Partial Search: TRUE

Ignore Case: TRUE

Description: EMPTY

 

But when using that search predicate on the Filter Rail, it's returning incorrect values. For example, searching for the word "Transtacker" returns an asset that contains this metadata:

 

{
"jcr:primaryType":"nt:unstructured",
"jcr:mixinTypes":[ "cq:Taggable" ],
"dam:Physicalheightininches":"2.8933334350585938",
"dam:Physicalwidthininches":"2.013333320617676",
"dam:Fileformat":"JPEG",
"dam:Progressive":"no",
"xmp:Rating":"5",
"tiff:ImageLength":868,
"exif:ColorSpace":65535,
"jcr:lastModifiedBy":"admin",
"xmp:CreatorTool":"Adobe Photoshop 6.0",
"dam:extracted":"Thu Jul 01 2021 17:03:44 GMT+0000",
"dc:format":"image/jpeg",
"dc:description":"very narrow aisle, transtacker",
"dam:Bitsperpixel":24,
"exif:ExifVersion":"0221",
"dc:rights":"The Raymond Corporation",
"dc:subject":"SDelucia",
"xmpMM:DocumentID":"A67E957E1CA871B76F90B89AFCD5C06B",
"xmpRights:Marked":true,
"dam:MIMEtype":"image/jpeg",
"tiff:Orientation":1,
"dam:Physicalwidthindpi":300,
"dam:Physicalheightindpi":300,
"trcProductStatus":"Current Production",
"xmpMM:OriginalDocumentID":"A67E957E1CA871B76F90B89AFCD5C06B",
"dc:modified":"Mon Oct 18 2021 14:04:29 GMT+0000",
"dam:Numberofimages":1,
"xmp:MetadataDate":"Wed Sep 28 2016 14:32:00 GMT-0400",
"jcr:lastModified":"Mon Oct 18 2021 14:04:29 GMT+0000",
"dam:Numberoftextualcomments":0,
"xmpMM:InstanceID":"xmp.iid:856dbebf-1767-0f4e-8615-8dbb402f4d8f",
"trcBrand":[ "raymond:brand/the-raymond-corporation/raymond" ],
"tiff:ImageWidth":604,
"dam:sha1":"bc858f1b0f2487042bdf74cb995cce0df18da360",
"dam:size":154599,
"trcProducts":[ "raymond:products/family/transtacker/trt" ],
"dc:title":"transtacker"
}

As you can see, it doesn't even contain the metadata field the Predicate refers to (trcmilsProductFamily). However, simply by having the search keyword ("transtacker") in other fields, it's being returned.

The expected behavior is that only assets which contain the search keyword in the correct metadata field should be returned.

 

It's important to note that, as far as we can tell, disabling Partial Search seem to fix this issue, no more false positives are reported.

 

 

Akash_Kapoor
Akash_Kapoor
Employee
November 22, 2021

Hi arctouch-emanuelmachado,

 

Thanks for raising the request but it would be great if you can share the detailed steps to see the current and expected behavior. Also, I agree that support ticket is a right channel when in doubt about bug/improvment so feel free to raise a follow up of the support ticket mentioned and we can priortise the same internally. We can use experience league ideas section to suggest new ideas/suggestions for the product.

 

Thanks,

Akash

Terms & ConditionsAccessibility statement

Loading footer...