-
Notifications
You must be signed in to change notification settings - Fork 9
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
search of partial "string" #345
Comments
wildcards should be avoided where possible as they slow things down so
asking TopCAT to slow down all queries to cope with this case is not a good
idea. Leading wildcards are especially bad. I will think about how best to
address the issue in the icat.server rather than TopCAT
…On 7 July 2017 at 09:55, Silvia da Graca Ramos ***@***.***> wrote:
At DLS, it was noticed that if we introduce a partial string for search
this does not work properly due to the separator used. The main issue was
with separator _ but more restrictions are still possible.
For example:
Search field: 54192
will not return all datasets and datafiles containing 54192. The solution
was to use *54192* which is not user friendly.
I have tested it and it is ok except when we have a . (dot) in the string.
For example 54192_Liver_area3_1.* will not return anything.
A possible solution will be to add automatically * as prefix and suffix.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#345>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACcg9mDC_0DXe50KZdzTtUtgOHzCtJauks5sLfKfgaJpZM4OQq86>
.
|
This issue needs to be solved as the search result is giving the wrong result to the user. |
Sorry it was closed in error |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At DLS, it was noticed that if we introduce a partial string for search this does not work properly due to the separator used. The main issue was with separator _ but more restrictions are still possible.
For example:
Search field: 54192
will not return all datasets and datafiles containing 54192. The solution was to use 54192 which is not user friendly.
I have tested it and it is ok except when we have a . (dot) in the string. For example 54192_Liver_area3_1.* will not return anything.
A possible solution will be to add automatically * as prefix and suffix.
The text was updated successfully, but these errors were encountered: