[digiKam-users] Import does not recognize existing images

[Nino]

Thank you Maik for the quick response.

> Otherwise, the unique digiKam file hash may already have changed after
the import due to metadata operations during the import, e.g. document name
was written or automatic image rotation.
This is not the case, since my script computes the hash in the same way as
Digikam does (i.e. uniqueHashV2) and I can clearly find all the images.

> Since we already started redesigning the import process in
digiKam-8.0.0-Beta,
> it would be possible to check for the unique digiKam file hash after
importing
> the file. However, this would require that all import options that would
modify
> the file are disabled and that the original file in the digiKam Album has
never
> been modified
That's actually my use case. I'm using Digikam mainly as an image database
and don't modify images nor metadata.

> This is not really user friendly. A solution with our duplicates search
is more conceivable.
My problems with duplicate search are:
1. It's quite slow to generate the fingerprints
2. It's quite cumbersome to remove the duplicates one by one.
I have a lot of duplicates in my Database and I need to have some automated
way of doing this. Maybe I can re-write my script to be based on
fingerprints instead of unique hash.

Cheers,
Nino

Am So., 5. Feb. 2023 um 12:24 Uhr schrieb Maik Qualmann <
metzpinguin at gmail.com>:

> We already have bug reports and wishes for this import problem. When
> importing
> items from camera devices or USB media, we use a mix of device, file name,
> file
> size, file date to recognize files that have already been imported. The
> unique
> digiKam file hash is not suitable for this as we do not have access to the
> file
> on GPhoto2 devices. Otherwise, the unique digiKam file hash may already
> have
> changed after the import due to metadata operations during the import,
> e.g.
> document name was written or automatic image rotation.
>
> Since we already started redesigning the import process in
> digiKam-8.0.0-Beta,
> it would be possible to check for the unique digiKam file hash after
> importing
> the file. However, this would require that all import options that would
> modify
> the file are disabled and that the original file in the digiKam Album has
> never
> been modified. This is not really user friendly. A solution with our
> duplicates
> search is more conceivable.
>
> Maik
>
> Am Sonntag, 5. Februar 2023, 11:30:20 CET schrieb Nino:
> > Hi folks,
> >
> > I was writing a small script that moves all duplicate images of my
> > Digikam database
> > to another folder:
> > https://github.com/ninok/digikam-utils/blob/main/move_duplicates.py
> >
> > To double check that the script did the right thing, I was trying to
> > re-import the duplicates.
> > I was expecting that the import will mark none of the images as new, but
> > instead all of the images are marked as new.
> >
> > I wrote another script that checks if there is a copy of each duplicate
> and
> > it works as expected:
> >
> https://github.com/ninok/digikam-utils/blob/main/safe_remove_duplicates.py
> >
> > Am I doing sth. wrong? How can I prevent import to import images that are
> > already in the database?
> >
> > Best regards,
> > Nino
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20230205/c3fa67cd/attachment.htm>