-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
Requested features:
|
An issue with AND/OR has been fixed by 48ecb69. Other features already exist:
|
The default still needs to be AND. At the moment:
|
This is because GraphDB's Lucene Connector implementation uses the default Lucene operator behavior which is OR. Unfortunately the plugin is closed-source, but we can always contact OntoText support about it. |
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? |
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. |
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.
The text was updated successfully, but these errors were encountered: