Expand my Community achievements bar.

Wildcard case-sensitive dc:description

Avatar

Level 3

Hi there,

I need to perform a case-insensitive search on the dc:description (AEM 6.5) metadata through the Querybuilder

Any help?

Thanks,
Serena Pitotti

8 Replies

Avatar

Community Advisor

@serenapitotti Could you please try with below?

 

property=@jcr:content/metadata/dc:description 

property.value=test

 

It should do full text search on that property , try wildcard and see if it works

Ref: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/ampersand-character-in-que...

 

you can also check the custom predicate options too

https://www.danklco.com/posts/2020/11/case-insensitive-queries-aem-query-builder.html

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/develo... 

 

Avatar

Community Advisor
property.operation=equalsIgnoreCase check if property equals ignoring case

 

fulltext It is used to search terms for fulltext search
fulltext.relPath the relative path to search in (eg. property or subnode) eg. fulltext.relPath=jcr:content or fulltext.relPath=jcr:content/@cq:tags

 

Please check this one too.

https://github.com/paulrohrbeck/aem-links/blob/master/querybuilder_cheatsheet.md

 

 

Avatar

Community Advisor

Hi @serenapitotti 

 

You can try the approach suggested in this blog - https://blogs.perficient.com/2020/11/11/case-insensitive-queries-with-the-aem-query-builder/

 

It talks about creating a custom predicate that you can then use in your query.

 

Thanks

Narendra

Avatar

Community Advisor

Did i understand the situation correctly, that a case sensitive search works through the Querybuilder?
And your situation is, that something is messed up in dc:description,
so you don't get all the search results that you need?

I am sorry for even bringing up this approach.
It is definitly not the solution you have asked for, but it could be a quick way forward on your current situation.

Maybe it is a good idea to export your metadata via the csv export function,
then clean-up this metadata property a bit - and then import it back into AEM.

Avatar

Level 3
  • Yes, case sensitive search works.
  • Nothing is messed up, simply my data on dc:description are not only lower case written
  • That's not a solution since I need my data as they are written

 

Thank you anyway.

Avatar

Administrator

@serenapitotti Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni

Avatar

Level 3

Need to try the solution with custom properties but no out of the box solution found.