Search doesn't show tags added from the recognize app

[hartsberger]

Which version of recognize are you using?

4.3.2

Enabled Modes

Object recognition

TensorFlow mode

Normal mode

Downstream App

Files App

Which Nextcloud version do you have installed?

26.0.7

Which Operating system do you have installed?

Ubuntu 22.04

Which database are you running Nextcloud on?

PostgreSQL 14.9

Which Docker container are you using to run Nextcloud? (if applicable)

No response

How much RAM does your server have?

16 GB

What processor Architecture does your CPU have?

x86_64

Describe the Bug

If you use the unified search to find files with a specific tag, those files don't show up in the search results if the tag was created from the recognize app. They only show up if you type only the first 2 characters of the tag. If you type 3 or more characters of the tag, they don't show up.

Expected Behavior

Those files should be listed in the search results like any other manually tagged files.

To Reproduce

1. Give a random file a tag that was created by the recognize app. e.g. "backpack" (Select a file, click on details , 3-dot-menu, tags)
2. reload the page and see, that the tag was applied to that file (shows up in activity)
3. Use the unified search: a. type in "back" --> no results b. type in "backpack" --> no results c. type in "ba" --> get all results (including files with the tag "backpak")

Debug log

No response

[github-actions[bot]]

Hello :wave:

Thank you for taking the time to open this issue with recognize. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. (Also see our Code of Conduct. Really.)

I look forward to working with you on this issue Cheers :blue_heart:

[marcelklehr]

Hi @hartsberger

Is this specific to tags created by recognize? Could you try creating a tag yourself and doing the same steps?

[marcelklehr]

Also, I notice the tag you mentioned "backpack" is spelled lowercase. In recent versions recognize tags are always uppercase :thinking: Maybe this is a legacy tag from an old version of recognize? Have you tried "Backpack"?

[hartsberger]

Hi @marcelklehr you were right. My fault was to type the tag in lowercase. As soon as I typed in "Backpack" the search results are as expected.

I would then ask if it is possible to change the current tag search from case sensitive to case insesnitive.

Every other search type (at least I tested files, apps, talk messages, deck cards) is not case sensitive. And no user would expect the requirement to type the first character in upper case. This would greatly enhance the UX.

Thank you.

[marcelklehr]

I would then ask if it is possible to change the current tag search from case sensitive to case insesnitive.

Agreed. This is not an issue for this repo, though, but rather for nextcloud/server -- if you are a Nextcloud customer, you may file this as a support ticket to get it fixed faster.