[Digikam-devel] [digikam] [Bug 318530] New: add a mode that only writes changed meta data to sidecar files

[Christoph Anton Mitterer]

https://bugs.kde.org/show_bug.cgi?id=318530

            Bug ID: 318530
           Summary: add a mode that only writes changed meta data to
                    sidecar files
    Classification: Unclassified
           Product: digikam
           Version: 3.1.0
          Platform: Other
                OS: All
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Sidecar Management
          Assignee: digikam-devel at kde.org
          Reporter: calestyo at scientia.net

Hi.

I think sidecar files should allow to basic modes of usage:
1) Write all known metadata to the sidecar files
This seems to be what we have now, although not really everything seems to be
written, e.g. all the MarkerNote data is NOT in the sidecar files.
I must admit that I do not see any real use case where one wants to do this in
contrast to (2) below.

2) Write only changed data to the sidecar files.
IMHO this is actually the main way how things should be used...
sidecar file in principle suck for many reasons but they have two big usage
scenarios:
a) when you don't want to modify the meta-data of the image themselves (i.e.
one just want's to override something, like a description or geodata)
b) when one can't change the meta-data easily for technical reasons (e.g. would
corrupt the image, confuse other software, or one wants to add so much data
that simply can't be encoded in the binary meta-data chunks
(a) is IMHO the main reason here.

What I tried was taking an image, and overriding it's camera model field, what
I got is however the big attached xmp file.
But IMHO:
<?xml version="1.0" encoding="UTF-8"?>
<x:xmpmeta xmlns:x="adobe:ns:meta/" x:xmptk="XMP Core 4.4.0-Exiv2">
 <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
  <rdf:Description rdf:about=""
   tiff:Model="foobarcamera             ">
  </rdf:Description>
 </rdf:RDF>
</x:xmpmeta>
should have been enough (well perhaps some xmlns are missing).
btw: Why tiff:Model? Shouldn't this be some exif:foo property?

The "same" happens (right now) when I go to the maintenance mode and rebuild
the meta-data... all files get XMP sidecar files, even nothing at all has
changed on them.


I personally think mode (2) would be enough, i.e. only storing changed data to
the sidecar files, but at least there should be an option which makes it doing
only this... there's not much reason for this meta-data duplication.


Cheers,
Chris.

Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.