Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the functioning of the Full Text Search functionality #55

Open
rtroncy opened this issue Nov 12, 2022 · 6 comments
Open

Update the functioning of the Full Text Search functionality #55

rtroncy opened this issue Nov 12, 2022 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@rtroncy
Copy link

rtroncy commented Nov 12, 2022

It seems that currently, the Full Text Search functionality works as an exact string match between the search terms and the textual items, and that an OR operator is being used when multiple terms are entered. This has confused hackathon participants.

Participants wish to rather have a AND by default (when multiple search terms are used) and maybe the possibility to express a OR or a quoted string.

Another option is to rely on SentenceBERT or equivalent. GraphDB does offer embeddings based search to investigate.

@rtroncy rtroncy added the enhancement New feature or request label Nov 12, 2022
@pasqLisena
Copy link
Member

Requested features:

  • AND (default) and OR
  • quoted
  • wildcard character *

@ehrhart
Copy link
Contributor

ehrhart commented Nov 23, 2022

An issue with AND/OR has been fixed by 48ecb69.

Other features already exist:

@rtroncy
Copy link
Author

rtroncy commented Nov 23, 2022

The default still needs to be AND. At the moment:

@ehrhart
Copy link
Contributor

ehrhart commented Nov 23, 2022

This is because GraphDB's Lucene Connector implementation uses the default Lucene operator behavior which is OR.
In order to change the behavior you would have to do it programatically during the instantiation of the QueryParser, by calling setDefaultOperator(QueryParser.Operator.AND)

Unfortunately the plugin is closed-source, but we can always contact OntoText support about it.

@rtroncy
Copy link
Author

rtroncy commented Nov 23, 2022

Thanks for digging this up! I'm all for contacting Ontotext and I have good relay there is needed. @ehrhart How would you like to proceed? Email or open an issue in some of their github?

@dschwabe
Copy link

I believe that there should be (possibly a minimal) help text in the tool itself, so that users have a better understanding of at least the default interpretation, until further options are available.

@rtroncy rtroncy assigned rtroncy and unassigned ehrhart Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants