Description
The site has a complicated and hard to use search.
Why?
-
It is not clear how good the full-text word search is. Nowhere is it explained what the search can find and what it cannot.
-
It is not possible to search by full EAN code,
-
you can't search by part of the EAN code, with a wildcard to limit the search to a specific country. For example 123*
-
the search distinguishes between letters with accents.
However, users who don't use the accented alphabet in their own language will enter the product name without it, which is wrong, e.g. á=a š=s č=c etc. -
the search is limited to whole words. Thus, you can't find a product with a misspelled name, or only part of the name.
-
the search intentionally does not show results from the search word if it is already contained in the product's brand name, this may not be clear to the user
why this is important:
- many users enter products incorrectly into countries where they are not on sale. This happens because they are expats or tourists and have their own language and country set as the main one on their mobile. Or using custom mobile apps with their custom settings. In a foreign country, they no longer change this setting and enter the food under their own country.
This is also why there are many products in the database "from France" although they may not be from France. Only in France there are most users who scan and enter products from different countries into the OFF database. Correcting these products is very time consuming.
Either figure out how to reduce this behavior or teach users from France to enter products exactly by the country where they scanned it. Learn users to enter the names of products precisely.
It is very hard for other users to subsequently edit the local country database. if we don't know the exact name of the food, it is hard to find it.
Also, there is no way to batch correct or delete multiple erroneous products at once, but this functionality belongs more in the "bulk editing of products and rights to those edits" topic
How to improve it:
-
Create a fully full-text search without the restrictions the user expects from a full-text search (including the ability to wildcard or exclude search strings)
-
work accurately and well with all NON-ASCII characters, especially with accented characters
-
if it is not possible, please explain the limitations of the web search
Metadata
Assignees
Type
Projects
Status
To discuss and validate
Status
To do
Status
Backlog (ready for dev)