Investigate and implement no truncation words by default
Description
ui-inventory right truncates all search terms without the operator explicitly asking for it. This is a remain of the type-ahead functionality which has been removed and replaced with an explicit search submit button. The implicit truncation should be removed.
Per this is the expected behavior for this change:
Searching instance by "Al Gore" would give results including "Al Gore" and "Al Gore and Global Warming"
Searching instance by "Al Go" would not return either
Searching by Al Go* would return "Al Gore", "Al Gore and Global Warming" and "Al Gorring" (we have verified that the UI doesn't escape the * character now so, we expect that the user should be able to use it as a wildcard to do explicit right truncation, if needed after this change has been made)
Hi - I have now done the manual test of this jira ticked, and performed searched on each of the spec'ed searches in the description. All looks good, and I'll close the ticket as done. Thanks.
Charlotte Whitt April 3, 2019 at 1:37 PM
Edited
Hi - just tested search on Identifiers in Inventory - which use the automatic truncation. So out of 142 records (in FOLIO Snapshot), then you get 96 results, if you search on Identifier: 978 ... So one can only imagine how it will look like if we have 10 mio records
Charlotte Whitt April 2, 2019 at 2:10 PM
Agree - would it be possible to list all the common FOLIO defined 'search ways' which we support - like Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search etc.
With such a list, then it would be quite easy for POs and SMEs together to define how the search is expected to be executed element by element in their respectively apps.
Adam Dickmeiss April 2, 2019 at 1:44 PM
But also right truncation results in huge number of hits.. Eg you search for pop and get popular and so on.. It is more natural to use stemming (which is supported for some fields already)
Jakub Skoczen April 2, 2019 at 1:33 PM
truncation results in slow queries (poor performance) and it is currently applied to ALL terms in the Inventory. My understanding is that this is a left-over from when the Inventory app used auto-complete, and it is no longer the case. If there is no functional reasons why all terms should be truncated – it should be removed.
ui-inventory right truncates all search terms without the operator explicitly asking for it. This is a remain of the type-ahead functionality which has been removed and replaced with an explicit search submit button. The implicit truncation should be removed.
Per this is the expected behavior for this change:
Searching instance by "Al Gore" would give results including "Al Gore" and "Al Gore and Global Warming"
Searching instance by "Al Go" would not return either
Searching by Al Go* would return "Al Gore", "Al Gore and Global Warming" and "Al Gorring" (we have verified that the UI doesn't escape the * character now so, we expect that the user should be able to use it as a wildcard to do explicit right truncation, if needed after this change has been made)
has confirmed this is acceptable.