The same issue occurred in LR3 and also in LR4. I did not expect LR 4 to be any different.
The same image with the same name is in two folders. I want to be sure all the images are in the LR catalog so I used the import dialog with the box checked that says: "Do not allow import of duplicates."
The import window shows the images. When imported, a -2 is added to the file name.
The folder is on a different hard drive. Sometimes LR does not show any images to import, which means that the images are in the Catalog. For other folders LR shows images that are available for import, but then adds the -2 to the file name.
>The same image with the same name is in two folders. I want >to be sure all the images are in the LR catalog so I used the >import dialog with the box checked that says: "Do not >allow import of duplicates."
From your description, I can't tell if you desire both files to be managed in LR or not. If LR is asked to import a set of images, and during the import a file naming conflict arises, it will append a sequence number to the filename to resolve the conflict.
Have you removed some files from LR during editing but not deleted them from the harddrive? If so, LR will not flag these as duplicates (they're not in the catalog) but will append the -2 upon import as the file exists on the drive causing a filename conflict.
Also, I think I remember an issue with changing timezones messing with the LR's ability to recognize duplicates. i.e. importing while on travel with TZ adjustment and then reimporting again back home with a different TZ. Not sure if that 'feature' is still around though.
The time zone seems to be a factor in some cases, but not all.
I have the same image, with the same file name, with no time zone issues. This file is on two separate hard drives. In LR, using the import dialog and with the 'do not import duplicates' box checked,
LR allows the import of this file in the location it is in without adding a -2, and also to the same folder as on the other hard drive and this time adds the -2.
While this might not matter, because I had to re-import all the files into LR from various locations, it became important to know which files had been imported and which had not; because of this 'feature' I am not able to determine which files are not in LR without checking each one.
When the import is first initiated, are either of the files in the catalog? If not, LR is probably not checking for duplication across the import set, only for duplication of the import set against the catalog. If that's the case, the first instance of the file is imported, then when LR hits the second instance it must resolve the filename duplication and adds the -2.
I'm no expert on Import duplication, so a bit of a guess here...
neither file is in the catalog. But sometimes it will import without adding the -2 and sometimes it adds the -2. Why is it adding the -2? If the same file is in the Catalog, it should not allow an import.
I wonder if it has to do with being on a separate hard drive, but I don't see why that should make a difference.
I've got some tedious work to figure out which files are in the Catalog and which are not.
My idea for a back up is to have the backup folder array match the primary and have a separate Catalog for the backup. Then when the hard drive that has the primary on it fails, the I can use the backup as the primary. It will be on a separate hard drive.
If neither file was in the catalog at time of import, then I think that LR's behavior is predictable (if not desired).
You've selected a set of images to import, none of those images are currently in the catalog, so all the images are flagged for import. (I don't believe LR is looking across the set of selected images for duplicates, only for duplicates against the catalog) The import then begins, a file duplication error is found and the -2 is added to avoid the conflict. Even though you've asked LR to avoid duplicates, it is only checking for them to help flag the images for import, it does not come into play once the import begins.