Recognize does not obey ignore files for external storage about recognize HOT 7 CLOSED

I found the issue. The .nomedia files MUST be added via Nextcloud, not from another source. I suggest updating readme to include that.

from recognize.

Hello 👋

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 💙

from recognize.

Possibly related bugs
#653

from recognize.

mmmmh, I believed to have fixed this ages ago. Can you try putting the ignore file one level deeper instead of in the root of the storage?

from recognize.

Aha. We're getting closer. Did you run a scan after adding the file on the storage source directly (not through nextcloud)? That should make recognize recognize it (heh).

from recognize.

When I initially opened the bug I

1. Created the .nomedia via touch /Storage/.nomedia
2. Ran a manual scan via docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:classify and it started scanning the Books directory mounted in NextCloud at /admin/files/Storage/Books/
3. Created another .nomedia file via touch /Storage/Books/.nomedia
4. Ran another manual scan and it scanned the Books directory again
5. Opened bug

After your comment I saw this comment and decided to test if ignore files would also be ignored if not created inside NextCloud.

1. I deleted both the .nomedia files
2. Used the NextCloud GUI to upload a new .nomedia file to each of my subdirectories under my external storage except the one I want scanned
3. Ran another manual scan
4. This time it obeyed the ignore files and only scanned the one subdirectory I wanted it to.

from recognize.

1. Created the .nomedia via touch /Storage/.nomedia
2. Ran a manual scan via docker exec --user www-data -it nextcloud-aio-nextcloud php occ recognize:classify and it started scanning the Books directory mounted in NextCloud at /admin/files/Storage/Books/

This is the problem. Files created in the mounted storage will not be picked up by nextcloud unless you do a files scan (occ files:scan). Everytime you update your storage contents without involving nextcloud you must rescan the contents so nextcloud knows what's in there. Only then can you expect recognize:classify to work correctly.

from recognize.