Hi, great app, a few questions:
1) Duplicate files are often appended with (1) at the end of the filename; how can these be included in the name match? Search criteria options don't seem to be able to handle that.
2) how to identify burst mode photos?
3) After the search is complete and the duplicates are listed, is there a way to group the same folders together when many duplicates are always out of the same folders?
e.g. file1 found in foldera and folderb; file2 found in the same two folders. List these two files in the same expanding group, as their folders are the same.
The advantage is that to select which file/folder to keep would be much simpler as I would keep the files from the same folder in these cases.
See attachment for example.
a couple questions
Re: a couple questions
I've also ran into files appended with (1), (2), etc. and I think I just changed my search method from file name to comparing file contents (I was just searching photos so that was the easiest), but am curious about what is the best way using the file name search.
This documentation covers the different text comparison methods (SmartMatch, FuzzyMatch, WordMatch, etc.) and it seems like Example 2 is the closest to this use case - for that FuzzyPercent seems to have a slight advantage over SmartMatch and others (and is also quicker). I'm also wondering if I should have just enabled "Ignore certain strings in filenames" with "(1)/(2)/(3)" etc. (FYI multiple strings need to be separated with a slash as per this documentation). I probably also could have used "Ignore characters at the end of a file name" for 3 characters, but that may be a little sloppy for the other files without the (1), (2), etc. at the end.
This documentation covers the different text comparison methods (SmartMatch, FuzzyMatch, WordMatch, etc.) and it seems like Example 2 is the closest to this use case - for that FuzzyPercent seems to have a slight advantage over SmartMatch and others (and is also quicker). I'm also wondering if I should have just enabled "Ignore certain strings in filenames" with "(1)/(2)/(3)" etc. (FYI multiple strings need to be separated with a slash as per this documentation). I probably also could have used "Ignore characters at the end of a file name" for 3 characters, but that may be a little sloppy for the other files without the (1), (2), etc. at the end.
-
dmitriy-kirilovfam
- Posts: 3
- Joined: 14 Apr 2025, 13:22
-
that's how we all learned, we asked questions.
I used to feel same, but not anymore. Everyone here has been so willing to help.
I wouldn't hesitate to ask anything.
I used to feel same, but not anymore. Everyone here has been so willing to help.
I wouldn't hesitate to ask anything.
Re: a couple questions
1)
Search: Properties -> Name
Ignore characters: <sp>()
Ignore strings: 1/2/3
Something along those lines might work.
<sp> is a physical space. Might depend on what your words are.
date.js & date (1).js, has a space so you need to look for it.
date.js & date(1).js, does not have a space, so <sp> is irrelevant
Ignore stings (& without Ignore characters) could also be something like:
Ignore strings: (1)/ (2)/ (3)/(1)/(2)/(3)/
So that handles spaces or not, & up to 3 "dups".
Search: Properties -> Name
Ignore characters: <sp>()
Ignore strings: 1/2/3
Something along those lines might work.
<sp> is a physical space. Might depend on what your words are.
date.js & date (1).js, has a space so you need to look for it.
date.js & date(1).js, does not have a space, so <sp> is irrelevant
Ignore stings (& without Ignore characters) could also be something like:
Ignore strings: (1)/ (2)/ (3)/(1)/(2)/(3)/
So that handles spaces or not, & up to 3 "dups".
Code: Select all
js
js (1)
js (2)
date.js
date (1).js