Improve ingredient search

[rolandgeider]

At the moment, the ingredient search can be a bit... problematic when you want to find a specific product.

Some ideas:

• add an exact match, similar to what the exercises already support
• push ingredients already used by the user to the top (should probably also be user-controllable and would need some discussion first)
• control the number of results (can we do something like infinite scroll when we reach the bottom?)
• ...

[Ewin7]

A small improvement to the search would be to automatically look up manually entered barcode numbers in the Open Food Facts database. Right now, it only searches on camera scan. I can implement this, and maybe work on further improvements in the future.

[anjakDev]

What do think about adding common_name and brand to the existing trigram search on the name? It would make use of the common_name value, and searching for the brand might sometimes be useful too. Neither of these fields should be its separate search bar imo, but as an 'implicit' inclusion to the existing search field, it might make the hits better. I'd be happy to implement that, but since it would need a migration on the indexes of ingredients.py for the new GIN indexes on common_name and brand, I wanted to give a heads up and ask for your opinion.

[anjakDev]

As for the one improvement you (@rolandgeider ) already mentioned, I'd be a big fan of sorting up the items that a user has previously logged. I think we can easily make use of the LogItems entries for that and from a UX standpoint, it makes a lot of sense to show historically logged entries. It's very common to repeatedly eat and therefore log the same items. Maybe at some point we could even add an info like 'last logged on [insert-date]' in the details view or maybe even the search results list...

[rolandgeider]

oh yes, we definitely don't want a second search box for the brand.

We can add new indices for those, but we would need to do some tests with the full db and see if we really want to always search all three fields. While I guess users expect the search to be a bit magic, but from personal experience it's very frustrating when the returned results have (seemingly) nothing to do with what you entered. But I guess we can also just add those to the expanded search options and select which fields should be searched.

+1 for the 'last logged on [insert-date]', but that will probably need more changes to make it work