I've been a happy user of digikam 0.9.x for a long time now and have happily tagged nearly 40,000 photos. I just took the plunge and upgraded to v0.10 and I'm impressed with the changes. One thing worries me though, and that is what has happened to my hierarchical tags? I have tags like:
person/family/tim person/family/john person/friend/tim and I write the tags to my data files. With v0.9 I got tags of person/family/a etc but now the EXIF header only reports "tim" (and in the above example it would not distinguish "person/friend/tim" from "person/family/tim"). Looking around on the mailing list I see mention that digikam now uses a private "digiKam" XMP namespace for writing the true hierarchical tag and writes flat tags to the IPTC section. That's fine as well but I'd feel happier about it if 1. exiftool reported that it could find the digiKam namespace (or exiv2 could). Can someone tell me how? 2. digikam itself reported the values when using the metadata tab. It reports the IPTC information that was written to the file such as copyright and the flattened tags, but the XMP section is blank. ie if there was any proof at all that I actually ended up with the hierarchical tags in the file. It would still be nice if there was an option to store the hierarchical form in the IPTC section for export so that tools like Google Picasa or Lightroom could read them (especially given the ambiguity in my example above) [although I imagine that populating the LR XMP namespace would be more appropriate for Lightroom users] One other problem is I believe fixed in v1.0. That concerns the way that when digikam is writing tags to a file that was tagged by v0.9.x you end up with person/family/tim and "tim" in the file since the tags are not ever removed by digikam. I think beta2 fixed that but I'm unable to test at the moment. Thanks again for the software. It's the best app I have ever used. I'm just having trust issues with v0.10.0. Tim _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Friday 10 July 2009 10:13:31 Tim Jenness wrote:
> I've been a happy user of digikam 0.9.x for a long time now and have > happily tagged nearly 40,000 photos. I just took the plunge and upgraded to > v0.10 and I'm impressed with the changes. One thing worries me though, and > that is what has happened to my hierarchical tags? I have tags like: > > person/family/tim > person/family/john > person/friend/tim Yeah, that bug existed... Unfortunately don't know if it was fixed in later versions. > and I write the tags to my data files. With v0.9 I got tags of > person/family/a etc but now the EXIF header only reports "tim" (and in the > above example it would not distinguish "person/friend/tim" from > "person/family/tim"). Looking around on the mailing list I see mention that > digikam now uses a private "digiKam" XMP namespace for writing the true > hierarchical tag and writes flat tags to the IPTC section. That's fine as > well but I'd feel happier about it if > > 1. exiftool reported that it could find the digiKam namespace (or exiv2 > could). Can someone tell me how? > 2. digikam itself reported the values when using the metadata tab. It > reports the IPTC information that was written to the file such as copyright > and the flattened tags, but the XMP section is blank. digiKam supports XMP starting from 0.10.0 . That means that any XMP info will be added only for photos which were tagged in 0.10.0 (or later). You could also choose tool "Synchronise all images with database". But in your situation I don't advise it - data written to images will be this improperly imported. > ie if there was any proof at all that I actually ended up with the > hierarchical tags in the file. It would still be nice if there was an > option to store the hierarchical form in the IPTC section for export so > that tools like Google Picasa or Lightroom could read them (especially > given the ambiguity in my example above) [although I imagine that > populating the LR XMP namespace would be more appropriate for Lightroom > users] Recent SVN versions are supporting LR XMP namespace. m. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Exactly. I'm using 0.10.0 and I use settings to make it synchronise tags to files. But whatever I do I can't get a file to report the digiKam XMP namespace, not even digiKam itself in the XMP tag.
You could I feel kind of deflated with that statement. To say that I am no longer allowed to write tags to old files that were previously tagged in 0.9.x is to say that those files are now static and not allowed to change just because I installed better software. That seems wrong.
For export as well as import? Tim _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
2009/7/10 Tim Jenness <[hidden email]>:
>> >> > and I write the tags to my data files. With v0.9 I got tags of >> > person/family/a etc but now the EXIF header only reports "tim" (and in >> > the >> > above example it would not distinguish "person/friend/tim" from >> > "person/family/tim"). Looking around on the mailing list I see mention >> > that >> > digikam now uses a private "digiKam" XMP namespace for writing the true >> > hierarchical tag and writes flat tags to the IPTC section. That's fine >> > as >> > well but I'd feel happier about it if >> > >> > 1. exiftool reported that it could find the digiKam namespace (or exiv2 >> > could). Can someone tell me how? >> > 2. digikam itself reported the values when using the metadata tab. It >> > reports the IPTC information that was written to the file such as >> > copyright >> > and the flattened tags, but the XMP section is blank. >> >> digiKam supports XMP starting from 0.10.0 . That means that any XMP info >> will >> be added only for photos which were tagged in 0.10.0 (or later). > > Exactly. I'm using 0.10.0 and I use settings to make it synchronise tags to > files. But whatever I do I can't get a file to report the digiKam XMP > namespace, not even digiKam itself in the XMP tag. To support XMP, you need Exiv2 >= 0.16 > >> >> You could >> also choose tool "Synchronise all images with database". But in your >> situation >> I don't advise it - data written to images will be this improperly >> imported. > > I feel kind of deflated with that statement. To say that I am no longer > allowed to write tags to old files that were previously tagged in 0.9.x is > to say that those files are now static and not allowed to change just > because I installed better software. That seems wrong. >> >> > given the ambiguity in my example above) [although I imagine that >> > populating the LR XMP namespace would be more appropriate for Lightroom >> > users] >> >> Recent SVN versions are supporting LR XMP namespace. > > For export as well as import? Both. Gilles Caulier > Tim > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Fri, Jul 10, 2009 at 7:16 AM, Gilles Caulier <[hidden email]> wrote: 2009/7/10 Tim Jenness <[hidden email]>: Yes. I have 0.18.1. So I take it that there is surprise that digikam is not reporting the XMP data in the metadata tab? Tim
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Hum, go to Help/components Info and lok which Exiv2 version is used
during compilation. Also, look libkexiv2 version... Gilles Caulier 2009/7/10 Tim Jenness <[hidden email]>: > > > On Fri, Jul 10, 2009 at 7:16 AM, Gilles Caulier <[hidden email]> > wrote: >> >> 2009/7/10 Tim Jenness <[hidden email]>: >> >> >> >> > and I write the tags to my data files. With v0.9 I got tags of >> >> > person/family/a etc but now the EXIF header only reports "tim" (and >> >> > in >> >> > the >> >> > above example it would not distinguish "person/friend/tim" from >> >> > "person/family/tim"). Looking around on the mailing list I see >> >> > mention >> >> > that >> >> > digikam now uses a private "digiKam" XMP namespace for writing the >> >> > true >> >> > hierarchical tag and writes flat tags to the IPTC section. That's >> >> > fine >> >> > as >> >> > well but I'd feel happier about it if >> >> > >> >> > 1. exiftool reported that it could find the digiKam namespace (or >> >> > exiv2 >> >> > could). Can someone tell me how? >> >> > 2. digikam itself reported the values when using the metadata tab. >> >> > It >> >> > reports the IPTC information that was written to the file such as >> >> > copyright >> >> > and the flattened tags, but the XMP section is blank. >> >> >> >> digiKam supports XMP starting from 0.10.0 . That means that any XMP >> >> info >> >> will >> >> be added only for photos which were tagged in 0.10.0 (or later). >> > >> > Exactly. I'm using 0.10.0 and I use settings to make it synchronise tags >> > to >> > files. But whatever I do I can't get a file to report the digiKam XMP >> > namespace, not even digiKam itself in the XMP tag. >> >> To support XMP, you need Exiv2 >= 0.16 > > > Yes. I have > 0.18.1. So I take it that there is surprise that digikam is not reporting the XMP data in the metadata tab? > Tim > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Fri, Jul 10, 2009 at 8:15 AM, Gilles Caulier <[hidden email]> wrote:
Hum, go to Help/components Info and lok which Exiv2 version is used Interesting. Had not noticed that menu yet. It says that Exiv2 supports XMP metadata LibExiv2 = 0.18.1 LibKExiv2 = 0.5.0 KDE 4.2.4 Tim _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
On Fri, Jul 10, 2009 at 8:37 AM, Tim Jenness <[hidden email]> wrote:
Aha. I downloaded and installed v1.0.0-beta2 to see if that had the same problem. It did. I found this curious so I dug a little deeper. It turns out that is possible to compile LibExiv2 0.18.1 with XMP support *disabled* and that is the default on gentoo unless the "xmp" use flag is enabled. So even though digikam reported that Exiv2 supported XMP metadata it doesn't seem to have actually asked Exiv2. Rebuilding libexiv2 with XMP enabled fixed the problem. beta2 does suffer from a bug though since the tags in the database are always one step out of sync with the tags written to the file. -add tag in database. No tag in file. - add second tag in database, First tag in file - remove first tag in database, Both first and second tag in file - add back first tag, Only second tag in file !! Does anyone else see this? I see that the LightRoom information is written to the file (as reported by ExifTool) but that namespace is not reported by the XMP metadata tab. I have noticed that the XMP metadata tab does not update without leaving the image and clicking on it again. Tim _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Free forum by Nabble | Edit this page |