[MGNLUI-464] Case insensitive search does not work Created: 21/Dec/12  Updated: 16/Dec/13  Resolved: 28/Oct/13

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 5.0
Fix Version/s: 5.2

Type: Bug Priority: Major
Reporter: Andreas Weder Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: framework, search, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Bildschirmfoto 2012-12-20 um 10.40.01.png     PNG File Bildschirmfoto 2012-12-20 um 10.41.08.png     PNG File Bildschirmfoto 2012-12-20 um 10.41.24.png    
Issue Links:
dependency
depends upon MAGNOLIA-5425 Update to latest stable JR 2.6.4 Closed
relation
is related to MGNLUI-2523 Searching for property with camelCase... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Sprint: 5.2-beta1

 Description   

For web pages, searching should typically work on:

  • the page name/URI
  • the page title

We should discuss, if it should also work on these fields - I think it should:

  • the template name: it would be very convenient, but:
  • this could clutter the search results with additional entries
  • this will eventually be covered by column filtering (and advanced search)
  • the navigation title: it's not visible by default so it's kind of hard to know why there's a match

In the attached images:

  • If I enter "pur", I don't get any matches: we should get the PUR* entries.
  • If I enter "PUR", I don't get any matches either. We should get the same entries.


 Comments   
Comment by Federico Grilli [ 03/Jan/13 ]

Search on page name should already be working (probably fixed by MGNLUI-460). As to case insensitive search, that would be easy to implement by using JCR lower() function, something along these lines

select * from [mgnl:page] as t WHERE lower(localname()) LIKE 'pur%' OR contains(t.*, 'pur')

however there's a known bug in JR https://issues.apache.org/jira/browse/JCR-3398 preventing that from working. It would work by omitting the "OR contains" part but then search would only work on node names.

Comment by Federico Grilli [ 03/Jan/13 ]

I provided a patch and a test case to jackrabbit. Hopefully they will include the fix in 2.4.4

Comment by Federico Grilli [ 12/Aug/13 ]

Since JR folks reaction on my patch submission has been null so far, today I tried to ask them again for a feedback. Should nothing happen the only option we have is to patch that class ourselves. Or just live with case insensitive search not working.

Comment by Federico Grilli [ 12/Aug/13 ]

Well, they just accepted my patch and fixed the issue https://issues.apache.org/jira/browse/JCR-3398 which should be delivered with JR 2.6.4. Once the latter is out, we will be able to easily solve our own issue.

Comment by Andreas Weder [ 12/Aug/13 ]

Great. And congrats in getting your patch in! You're now an official Jack the Rabbit.

Generated at Mon Feb 12 08:37:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.