Summary: | Write file versioning information from database into XMP metadata | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Stéphane Bidoul <sbi> |
Component: | Metadata-Versioning | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | caulier.gilles, randy |
Priority: | NOR | ||
Version: | 4.3.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Stéphane Bidoul
2014-09-21 18:08:28 UTC
The image history which contain already versioning information into XMP digiKam namespace. This is not enough ?
Exemple:
>>> digiKam schema <<<
CaptionsAuthorNames :
CaptionsDateTimeStamps :
ColorLabel : 0
ImageHistory : <?xml version="1.0"?> <history version="1"> <file uuid="6251a840d7847a86ab79fdf351fb6f38eee940ca139c4164fadfa0b829f48166" type="original"> <fileParams fileName="640_IMG_6906_Kapliczka_v1.JPG" filePath="/mnt/data2/photos/TESTS/" fileHash="eee940ca139c4164fadfa0b829f48166" fileSize="119049" creationDate="2013-11-28T16:07:25"/> </file> </history>
ImageUniqueID : ad340046be0d63810f21bd2c03302ec7eee940ca139c4164fadfa0b829f48166
PickLabel : 1
Gilles Caulier
Hello, I have seen the ImageHistory field, but I could not find in it the information that a specific version is hidden. For instance, when you create a version from the original, v1 has the ImageHistory field, but the original does not, and there is no way to know that the original should be hidden. version 1: ImageUniqueID : ad340046be0d63810f21bd2c03302ec7eee940ca139c4164fadfa0b829f48166 version 2: ImageHistory : <?xml version="1.0"?> <history version="1"> <file uuid="6251a840d7847a86ab79fdf351fb6f38eee940ca139c4164fadfa0b829f48166" type="original"> ... This is how digikam determines versions. Version 2 points back to the ID of version 1. There's an option in settings to show or hide originals. |