OK, let me expand a little.
I'm using this rule to organize iPhone photo imports (moving videos into a Master Videos directory, photos into a Master Photos directory, which then gets backed up each night, locally and offsite). The rule also auto-organizes the files based on YYYY-MM directories. This is all working great.
So, scenario #1 (typical): I forget to delete the archived photos from my iPhone, shoot more photos, then on the import, all the photos I already imported previously are imported again, along with the new photos. Since I don't need duplicates, I'd like Hazel to "ignore" them (or "throw them away"—though, ideally, I'd like them to go into a "Safety Net" folder I've created, but that's another thread...). This is all good.
But, scenario #2 (pretty random, but I'm paranoid of losing photos): A completely different photo (or even a modified version of the photo) is imported with the same name. While the contents of the file are different, the name is the same (say, the photo was retouched)—so, this is where I'm not sure what would happen. Since the files have the same name, would they be considered "duplicates" (thus one of them is "thrown away"), or would Hazel understand that, even though they have the same name, they're not actually duplicates and thus re-name (appending "-1" or whatever) to the second file upon import? I realize this is being paranoid, but just like to get everything sorted before automating a process like this).
Thanks again,
Kristin.