In duplicate searches with multiple search paths, there could be source location(s) e.g. “D:DATApictures; D:DATAimages” and secondary location(s) “:X:backupfoto;X:CLONEprivate”
It would be useful to only select duplicates that are present in the primary AND in the secondary location. That way you could make sure to only discard duplicates on the X drive (in this example) where a "matching" original file is found on drive D:
Example : file present in D:DATApictures and in D:DATAimages but nowhere on the X drive -> No files will be checked Example : file present twice but only on the X drive -> No files will be checked Example : file present in D:DATApictures and in X:backupfoto -> All files in X:backupfoto will be checked
Allow finding, post search filtering, and/or selecting (check/uncheck) duplicates only when they appear on one or more specific paths.
So if I search across 4 drives, I want to know they at least one of the duplicates is on the 1st drive (or also the 2nd one).
Background - I am searching a couple older drives against a current drive and want to know which files might not have been moved from the old drives.
As it is now, I get a lot of hits across just the two older drives which are not very helpful in this case.
I would appreciate more options for duplicate file searches.
Specifically I'm missing options to filter duplicate file search results or more flexibility with the "Check if" filters.
Only show result groups which contain files from a specific folder (or other criteria). In the next step I would like to be able to only check files by a specific criteria that are contained in this filtered result list.
I search in folders A, B and C. All duplicate files might be contained in all 3 folders or only in 2 of them. I want to delete all files from B and C that are already contained in A. But if they are not contained in A I don't want them to be deleted from B or C. With result filters I could filter all groups not containing files from A and proceed with the remaining subset of results.
Currently I would have to do 2 searches: one with A and B and one with A and C because searching all 3 folders for duplicates would also show me groups only containing duplicates in B and C that are not contained in A.
Alternatively this could also be achieved with adding exceptions to "Check if" patterns.
Generally this request is only an example. There are much more cases in which more comprehensive configurable patterns and filters would be very handy.
The software "Alldup" could be inspirational for several other options.
Thank you for your input and feedback. Please understand that need more focused and concrete feature requests on this platform. This important to properly handle duplicates and status. I am going to merge this request in a very similar one.
A question before I answer. What do you mean by being checked.
My defintions :
"seached" = filter that determlnes the folders and files to be compared between each other
"found" = files that wille be retained if a compare situation is forefilled. This basically the result list of "found duplicates"
"cheked" = the files in the complete "found" list that have been marked (manually or automatically) in order to perform an certain operation (e.g. delete these files)
Another possible addition would be to extend the "Check if" functionality in a way that you can "Check files from path A if they exist in drive B". That should also help with backup related use cases such as this.
Thank you very much for your suggestion. We do have a few questions regarding the examples that you provided. The way you describe it is not 100% well defined and it's not really clear what should happen in certain cases. What would be the expected behavior in the following case:
Example: file present in D:DATApictures mulitple times and also in X:backupfoto.
Would you show all of the copies located in D:DATApictures, or only one of them? If one of them, which one would you choose? In case of multiple ones, it would still be possible that the "Check all but oldest" function would select all of the files in your primary location.
The function that you described does not really ensure that only files from a specific drive are checked. How about the following, alternative approach? One idea that we already have in mind is the following:
-> Add a function to "lock" files that originate from certain paths, so that they can no longer be checked. That way, you could use the usual selection methods such as "Check all but newest" and still prevent the files from your "primary" locations to be checked in the result list.
Would that help with your use case? A function like that would be more generic and its behavior would be much clearer.