recognize icon indicating copy to clipboard operation
recognize copied to clipboard

Process only specific directories

Open dcowan-london opened this issue 2 years ago • 1 comments

Currently Recognize attempts to process all files unless the directory contains .noimage, .novideo or .nomedia (ie, opt-out).

I only want a few directories to be processed, eg the Photos directory. I'd like there to be an option in settings to switch to opt-in, and select the directories I want to be processed - all others should be ignored.

dcowan-london avatar Sep 28 '22 10:09 dcowan-london

I was looking for this as well. In fact came here to say this. Is it possible?

I need this mainly because I can't use noimage or other opt-outs as I want photos to see them and Audio/Music as well. May be a special ".recognize-scan" in directory to flag it for scan or ".dont-recognize" to ignore it is an option?

victoraroyo avatar Oct 06 '22 07:10 victoraroyo

.noimage, .novideo and .nomedia don't seem to work for me at all tbh, seems broken anywhere in nextcloud.

illnesse avatar Oct 10 '22 17:10 illnesse

This feature would be very usefull for me. Would live to see it!

Demian98 avatar Oct 19 '22 21:10 Demian98

I think it would be great if you could define a specific folder. For example the photo folder.

For example, I have a large music collection, with photos of the artists. Now I have the problem that these photos are also recorded, although I do not need them.

So I think this is an important feature.

NCC1701G avatar Nov 05 '22 14:11 NCC1701G

Fixed by #468

marcelklehr avatar Nov 08 '22 12:11 marcelklehr

Quick question - should we trigger a full reclassification of all images for this change to be applied, or will already tagged images be ignored if they are in a .nomedia folder?

jgonsior avatar Nov 08 '22 13:11 jgonsior

For normal tags, you shouldn't need a reclassification as the photos app should already filter those out. For face tags, you will need one.

marcelklehr avatar Nov 08 '22 13:11 marcelklehr

@marcelklehr It's been a while but I've just come back to this - sorry, but I'm not sure I see how #468 closes this issue? This issue does not seem to be fixed.

dcowan-london avatar Feb 10 '23 15:02 dcowan-london

This issue does not seem to be fixed.

Indeed. My mistake. Consider this closed as wontfix. Sorry.

marcelklehr avatar Feb 10 '23 16:02 marcelklehr