ZCU-PUB/Partial match for community/collection search

[Paurikova2]

Problem description

The DSO selector search only matched whole words, preventing users from finding communities/collections with partial text input (e.g., typing "t" wouldn't find "test" community).

@vidiecan This is a potential upstream PR.

Solution

Implemented partial prefix matching for communities and collections using dc.title:query* search format, enabling single character and partial text searches to find relevant results from the beginning of titles.

Manual Testing (if applicable)

• Added to testing scenarios

Copilot review

• Requested review from Copilot

[Paurikova2]

@milanmajchrak If we want to include this PR, we should also offer it to Vanilla and cherry-pick it for other customers (mainly dtq-dev).

[Copilot]

Pull request overview

This PR updates the DSO selector’s search behavior to support partial/prefix matching, primarily to improve discoverability of Communities/Collections when users type short or partial queries.

Changes:

• Adds query preprocessing to rewrite non-empty user input into a prefix/wildcard query.
• For Community/Collection searches, rewrites queries to a dc.title:<query>*-style fielded prefix query.
• Passes the rewritten query into PaginatedSearchOptions instead of the raw input.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

[Paurikova2]

@milanmajchrak I wanted to add it to scenarios earlier, but then I realized we should first merge it into dtq-dev (zcu-pub isn’t used for testing).

[Paurikova2]

Solr/Lucene query syntax is already used directly in Angular in several other places (search.resourceid: in dso-selector, -search.resourceid: in item-collection-mapper, -location.coll: in collection-item-mapper). Moving this logic to the backend would require a larger cross-cutting refactoring. This PR is consistent with the existing pattern.

[Paurikova2]

@vidiecan Because this PR is no longer a vanilla PR (recent changes in vanilla already fix this issue), we decided to only remove references to Solr/Lucene from comments and method names instead of moving the implementation to the backend. Also, what supported our decision is that Solr/Lucene query syntax is already used directly in Angular in several other places, not just by us.