Search function, finds what you are looking for

Oct 5, 2019

Oct 5, 2019
Oct 5, 2019
Oct 5, 2019

-

2 minutes

2 minutes
2 minutes
2 minutes
Search function, finds what you are looking for
Search function, finds what you are looking for
Search function, finds what you are looking for

Full Text Search

Of course, search functionality is mandatory in an application like our dynamicDAM® or dynamicPIM®. In line with our philosophy of keeping the complexity of our applications as low as possible, the search function is of significant importance. In an ideal world, it works like a search bar from Google and uses AI to find exactly what the user is envisioning. However, we are not quite there yet. We have positioned the search prominently and allow for high variability in the system by selecting the fields to be searched in the backend (index). As in many other cases, this primarily depends on individual configuration.

Auto-Complete Mechanics in the Frontend

Auto-Complete displays results of the search term directly in the results and highlights them in this case. You might also know this from Google. It enables a direct visual assessment of the results and leads to faster outcomes. We have integrated it into the search function to provide users with a better user experience.

Find Relevant Information, Even When Words Are Not Directly Combined

You might be familiar with this. You enter a text into the search and want to refine it because it yields too many results. When you enter more text, the search finds nothing anymore. This often happens because the search function only finds connected phrases, i.e., text components. However, if these terms are part of another text area, there are no results.

Here’s an example:

Search for: Persil laundry detergent 1 kg

First Input in Search: Persil

First Result: The search finds the mentioned product, but also all other Persil products

Second Additional Input: Persil 1 kg

Second Result: The search finds no results, as the search term is not connected

Solution: Our search recognizes all words and word components, even when they do not occur consecutively. In the mentioned example, it would find the product and only other products where the search terms “Persil” and “1 kg” appear. This may initially seem trivial, but in systems with more than 50,000 products, it can be a very decisive factor.

Error-Tolerant Search

In addition to the logic just described, an error-tolerant search can also be activated. This search allows for finding not only exact matches but also similar spellings and results. It can be an additional advantage or the exact opposite when error tolerance leads to nonsensical results, for example, with digits and numbers. In the specific case, one must decide whether activation is sensible.

Full Text Search

Of course, search functionality is mandatory in an application like our dynamicDAM® or dynamicPIM®. In line with our philosophy of keeping the complexity of our applications as low as possible, the search function is of significant importance. In an ideal world, it works like a search bar from Google and uses AI to find exactly what the user is envisioning. However, we are not quite there yet. We have positioned the search prominently and allow for high variability in the system by selecting the fields to be searched in the backend (index). As in many other cases, this primarily depends on individual configuration.

Auto-Complete Mechanics in the Frontend

Auto-Complete displays results of the search term directly in the results and highlights them in this case. You might also know this from Google. It enables a direct visual assessment of the results and leads to faster outcomes. We have integrated it into the search function to provide users with a better user experience.

Find Relevant Information, Even When Words Are Not Directly Combined

You might be familiar with this. You enter a text into the search and want to refine it because it yields too many results. When you enter more text, the search finds nothing anymore. This often happens because the search function only finds connected phrases, i.e., text components. However, if these terms are part of another text area, there are no results.

Here’s an example:

Search for: Persil laundry detergent 1 kg

First Input in Search: Persil

First Result: The search finds the mentioned product, but also all other Persil products

Second Additional Input: Persil 1 kg

Second Result: The search finds no results, as the search term is not connected

Solution: Our search recognizes all words and word components, even when they do not occur consecutively. In the mentioned example, it would find the product and only other products where the search terms “Persil” and “1 kg” appear. This may initially seem trivial, but in systems with more than 50,000 products, it can be a very decisive factor.

Error-Tolerant Search

In addition to the logic just described, an error-tolerant search can also be activated. This search allows for finding not only exact matches but also similar spellings and results. It can be an additional advantage or the exact opposite when error tolerance leads to nonsensical results, for example, with digits and numbers. In the specific case, one must decide whether activation is sensible.

Full Text Search

Of course, search functionality is mandatory in an application like our dynamicDAM® or dynamicPIM®. In line with our philosophy of keeping the complexity of our applications as low as possible, the search function is of significant importance. In an ideal world, it works like a search bar from Google and uses AI to find exactly what the user is envisioning. However, we are not quite there yet. We have positioned the search prominently and allow for high variability in the system by selecting the fields to be searched in the backend (index). As in many other cases, this primarily depends on individual configuration.

Auto-Complete Mechanics in the Frontend

Auto-Complete displays results of the search term directly in the results and highlights them in this case. You might also know this from Google. It enables a direct visual assessment of the results and leads to faster outcomes. We have integrated it into the search function to provide users with a better user experience.

Find Relevant Information, Even When Words Are Not Directly Combined

You might be familiar with this. You enter a text into the search and want to refine it because it yields too many results. When you enter more text, the search finds nothing anymore. This often happens because the search function only finds connected phrases, i.e., text components. However, if these terms are part of another text area, there are no results.

Here’s an example:

Search for: Persil laundry detergent 1 kg

First Input in Search: Persil

First Result: The search finds the mentioned product, but also all other Persil products

Second Additional Input: Persil 1 kg

Second Result: The search finds no results, as the search term is not connected

Solution: Our search recognizes all words and word components, even when they do not occur consecutively. In the mentioned example, it would find the product and only other products where the search terms “Persil” and “1 kg” appear. This may initially seem trivial, but in systems with more than 50,000 products, it can be a very decisive factor.

Error-Tolerant Search

In addition to the logic just described, an error-tolerant search can also be activated. This search allows for finding not only exact matches but also similar spellings and results. It can be an additional advantage or the exact opposite when error tolerance leads to nonsensical results, for example, with digits and numbers. In the specific case, one must decide whether activation is sensible.

Full Text Search

Of course, search functionality is mandatory in an application like our dynamicDAM® or dynamicPIM®. In line with our philosophy of keeping the complexity of our applications as low as possible, the search function is of significant importance. In an ideal world, it works like a search bar from Google and uses AI to find exactly what the user is envisioning. However, we are not quite there yet. We have positioned the search prominently and allow for high variability in the system by selecting the fields to be searched in the backend (index). As in many other cases, this primarily depends on individual configuration.

Auto-Complete Mechanics in the Frontend

Auto-Complete displays results of the search term directly in the results and highlights them in this case. You might also know this from Google. It enables a direct visual assessment of the results and leads to faster outcomes. We have integrated it into the search function to provide users with a better user experience.

Find Relevant Information, Even When Words Are Not Directly Combined

You might be familiar with this. You enter a text into the search and want to refine it because it yields too many results. When you enter more text, the search finds nothing anymore. This often happens because the search function only finds connected phrases, i.e., text components. However, if these terms are part of another text area, there are no results.

Here’s an example:

Search for: Persil laundry detergent 1 kg

First Input in Search: Persil

First Result: The search finds the mentioned product, but also all other Persil products

Second Additional Input: Persil 1 kg

Second Result: The search finds no results, as the search term is not connected

Solution: Our search recognizes all words and word components, even when they do not occur consecutively. In the mentioned example, it would find the product and only other products where the search terms “Persil” and “1 kg” appear. This may initially seem trivial, but in systems with more than 50,000 products, it can be a very decisive factor.

Error-Tolerant Search

In addition to the logic just described, an error-tolerant search can also be activated. This search allows for finding not only exact matches but also similar spellings and results. It can be an additional advantage or the exact opposite when error tolerance leads to nonsensical results, for example, with digits and numbers. In the specific case, one must decide whether activation is sensible.