[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #12 from caulier.gil...@gmail.com --- Maik, did you see the Jens proposal in this thread ? -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #10 from Jens --- If the uuid is only generated from the file *metadata*, just exclude the tag with the (previous) UUID when generating a new one. This requires generating the UUID not from the raw file text but from a parsed / cleaned /

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #9 from Maik Qualmann --- How can you write a UUID in the metadata, since the UUID of the file changes again after the metadata is written? Maik -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #8 from Jens --- You answered your own question about the purpose of the UUID in the metadata :-) My intention is to make this a (more) stable interface to make images uniquely identifiably *also across Digikam installations*. I have a

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #7 from Maik Qualmann --- The UUID (hash) used by digiKam is in the database, as is the image ID. What is the purpose of this information in the metadata? Other programs use other methods to create a UUID from the file. The UUID also

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 Jens changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Resolution|---

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 Jens changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 Justin Zobel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|---

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 --- Comment #1 from Jens --- Hi, can anything be done about this? This makes the import process of iphoto2xmp (see github -> jensb/iphoto2xmp) much harder and I don't really see why Digikam would need to regenerate a

[digikam] [Bug 363522] import: use UUID from XMP sidecar / metadata instead of creating another one

https://bugs.kde.org/show_bug.cgi?id=363522 caulier.gil...@gmail.com changed: What|Removed |Added Component|Import |Import-PostProcessing -- You are