[web] Enable Fulltext Search by default

[tbsbdr]

Description

User Stories

• As a user I want that the standard search searches in fulltext so that I get maximum searchresults.

Value

• improve file search behaviour
• consistent behaviour of search filters (all filter narrow down; currently "search only in content" extends the search results)

Acceptance Criteria

• klick on 🔍 searches in content and title per default (if fulltext search is not available -> title only, like it already is now)
• replace filter "search only in content" with "Title only" (if fulltext search is not available -> don't show the filter)
  • click on "Title only" narrows down search results for matches in the title only
• tech cherry on top: don't escape quotes anymore. @fschade claims that search works without escaping the quotes.

Definition of ready

• Everybody needs to understand the value written in the user story
• Acceptance criteria have to be defined
• All dependencies of the user story need to be identified
• Feature should be seen from an end user perspective
• Story has to be estimated
• Story points need to be less than 20

Definition of done

• Functional requirements
  • Functionality described in the user story works
  • Acceptance criteria are fulfilled
• Quality
  • Code review happened
  • CI is green (that includes new and existing automated tests)
  • e2e tests are adjusted to new behaviour
  • Critical code received unit tests by the developer
• Non-functional requirements
  • No sonar cloud issues

[AlexAndBear]

Not a fan. I'd rather search for content and title by default and omit the search in content filter completely

[tbsbdr]

Not a fan. I'd rather search for content and title by default and omit the search in content filter completely

Thats what I want too 👍
Plus: provide a "Title only" filter

[kulmann]

That would need a change in the backend search behaviour. At the moment you can only decide if you want content-search or filename-search, never both at the same time.

[tbsbdr]

ok, thanks for the remark @kulmann. do you agree that the std search should be title+content ?

[kulmann]

do you agree that the std search should be title+content ?

Yes, I do!

[micbar]

Please Clarify why this is a backend issue?

We support the KQL queries for searching for title OR content, what is missing?

[kulmann]

Please Clarify why this is a backend issue?

We support the KQL queries for searching for title OR content, what is missing?

We need a) title AND content or b) title only
Afaik title AND content is not possible at the moment... if I'm wrong then there's nothing to do in ocis.

Argh, sorry, that was bogus... we just want to be able to search in title AND content at the same time, but it's sufficient if the search term is only present in title OR content. However, I thought that the current implementation only allows a search in either title or content but not combined.

[ScharfViktor]

Create emptytext.txt and new.txt with some new text content
try to find by text

<oc:pattern>content:&quot;text&quot; OR name:&quot;*text*&quot;</oc:pattern> - 207 text.txt and new.txt in response

<oc:pattern>content:&quot;text&quot; AND name:&quot;*text*&quot;</oc:pattern> - 207 empty response.

a) title AND content

try to find by new using AND

<oc:pattern>content:&new;text&quot; AND name:&quot;*new*&quot;</oc:pattern> - 207 and only new.txt in response

[kulmann]

Updated my comment, title AND content was my fault, not what I intended to say, sorry.

[kulmann]

Ok, thanks @ScharfViktor - works like we need it. Transferring back to web.