Bug 234099

Created attachment 42702 [details]
iptc

Created attachment 42703 [details]
xmp

All are there, only in XMP, and XMP _only_, it's normal. IPTC has only tags list, not full tags pathes.

   <digiKam:TagsList>
    <rdf:Seq>
     <rdf:li>étiquette2/etiquette3</rdf:li>
     <rdf:li>étiquette2/etiquette3/étiquette4</rdf:li>
     <rdf:li>étiquette1</rdf:li>
     <rdf:li>essai</rdf:li>
     <rdf:li>étiquette2</rdf:li>
    </rdf:Seq>
   </digiKam:TagsList>

Gilles Caulier

i didn't well explain so
i made captures
in the first capture digikamhierarchy.png
in digikam you see the hierarchy 

in the second capture picasawebhierarchy.png
in picasaweb you see no hierarchy

Created attachment 42707 [details]
digikamhierarchy.png

Created attachment 42708 [details]
picasawebhierarchy.png

As far as I can tell, picasa simply doesn't support hierarchical tags. So what should the uploader do instead of flattening the tag tree?

Right

But which way picasaweb use to extract tag paths from XMP, and only XMP , because IPTC is very restricted for char encoding. I hope that PicasaWeb use XMP and NOT IPTC... else Picasaweb is a dinosaur (:=)))

Gilles Caulier

Jens,

PicasaWeb is a modern photo publishing web service... Thanks google (:=)))

Gilles Caulier

I'd vote to close this as invalid.

no you don't know well picasa and picasaweb
look what i made with digikam 0.9.6 and picasa and picasaweb
in the first capture digikam096hierarchy1.png
in digikam you see a photo with several hierarchies

i export this photo with picasa to picasaweb
in the second capture picasawebhierarchy_exported_with_picasa.png
in picasaweb you see same hierarchies

i made a third capture picasawebhierarchy_of_my_albums.png
in picasaweb you see my complex tags hierarchy

Created attachment 42709 [details]
digikam096hierarchy1.png

Created attachment 42710 [details]
picasawebhierarchy_exported_with_picasa.png

Created attachment 42711 [details]
picasawebhierarchy_of_my_albums.png

So #8 still valid.

If picasaweb do not support XMP as tag paths hosting, i suppose IPTC must used instead.

This is want mean that IPTC must be patched when images as exported. A copy of images must be created in fact. Do not patch IPTC keywords with tags paths directly on source files. IPTC keywords must host tag name, not tag path. 

Do not restore old way from digiKam to save tag path in IPTC keyword. It's a wrong way. XMP must be used intead. If google do not support XMP as well, it's not digiKam fault. Ask to goole to fix Picasaweb...

IPTC is old and obsolete way. XMP must be used instead. It's more powerfull, a modern way, and the most important : there is not limitation about char encoding and string size !

Gilles

To me, the old behaviour sounds like a bug, because picasa simply doesn't know how to handle a / in a tag name. They don't know anything about hierarchies for tags.

i conclude from your argument :
when i want to export my image i must use picasa and not picasawebexport
plus
i can't use picasawebexport for movie because geotag is not exported
then
i must keep on using picasa to export

what is the utility of picasawebexport ?

i don't understand your argument.
picasawebexport is an interface between digikam and picasaweb and must be compliant with picasawbeb not a futur picasaweb
an interface is there to transcode between 2 tools

digikam and picasaweb will never do same thing because each one changes continously

addendum:
- when i begun to speak (2 years ago ?) about xmp i was using digikam 0.8.x and i wanted digikam using xmp to export my photos to my other photo site (jalbum) using xmp.
at this time i added issues in picasaweb google group

http://www.google.com/support/forum/p/Picasa/thread?tid=7d83efb91f35a6f5&hl=en
http://www.google.com/support/forum/p/Picasa/thread?tid=4a951623033392f3&hl=en
http://www.google.com/support/forum/p/Picasa/thread?tid=04fb3284499546e7&hl=en

no replies since 3 may 2009

- yes there is a lovely feature in the new picasaweb the add-replace for photos
thanks to picasawebexport dev

No, I mean that I cannot see that picasa supports hierarchical tags in any way. The same is eg. true for flickr and many other web photo services. So from the view point of the picasa web service it doesn't make any sense to have tags in the form "a/b/c" because they don't know that this means b is a child of a. For this reason the current implementation does:
docMeta.createTextNode(Qt::escape(info.tags.join(","))); 
joining all leaf tags of the tag tree to the tag list used for the export.

Of course we can add an option to support the tags as it was in an older version but from picasa's point of view it doesn't make much sense. This is kind of decision always has to be made if two different approaches to model things need to be fused.

first case

you had copied hierarchies
in the futur picasaweb takes care of hierarchy
then
nothing to do to use them in picasaweb

second case
you had NOT copied hierarchies
in the futur picasaweb takes care of hierarchy
then
how do you do to use hierarchy for your old photos? will you supply a batch tool to update hierarchies from digikam ?

you say xmp is the new standard then all must use xmp.
yes
but when i update from 0.9.6 to 1.2 digikam well creates a sqlite 4 digikam db from sqlite3 digikam db but digikam does not copy exif or iptc data to xmp for my photos

AFAIK picasaweb do not provide tag hierarchies nor do picasa 3 do.

Also picasa 3 do not export xmp, only iptc tags, right? But Philippe, you made a attachment where you save a tagpatch (but handled as a single tag) into picasaweb. How do you do that?

Johannes, i think you missunderstand something (or do I?), kipi-exporter never exported tag paths (Philippe, right)?

Anyway, we could add a option to export full tag patch, even though it will be handled as one single tag. But should we? Are there any other applications doing it this way?

Jens

(In reply to comment #21)
> Johannes, i think you missunderstand something (or do I?), kipi-exporter never
> exported tag paths (Philippe, right)?

Ok, I thought he uploaded the other ones with an old version...

> Anyway, we could add a option to export full tag patch, even though it will be
> handled as one single tag. But should we? Are there any other applications
> doing it this way?

The Flickr plugin exports only child tags which is what I would expect when a tree is transferred to a flat list. I would not want the intermediate tags in my uploaded images. So, to my mind, it should be a user option which conversion to use.

 
(In reply to comment #21)
> Also picasa 3 do not export xmp, only iptc tags, right?
yes

> But Philippe, you made
> a attachment where you save a tagpatch (but handled as a single tag) into
> picasaweb. How do you do that?
> 
till today i use digikam 0.9.6 to manage my photo and picasa to export them to picasaweb

> Johannes, i think you missunderstand something (or do I?), kipi-exporter never exported tag paths (Philippe, right)?

yes

Adding that option is not that simple as I first thought. Tag are gathered via kipi-interface. Kipi-interface only provide a list of leaf tags. So the interface has to be modified to export the full tag paths here. This implies modifing all kipi-plugins which rely on the tags.

Jens

Jens,

In digiKam kipi interface, it's already do. You can ping all information from  Digikam::ImageInfo class, as for example rating info. Look there like TagsPath are handle with a QMap:

http://lxr.kde.org/source/extragear/graphics/digikam/utilities/kipiiface/kipiimageinfo.cpp#136

In plugin, just get the right properties like this :

http://lxr.kde.org/source/extragear/graphics/kipi-plugins/common/libkipiplugins/widgets/imageslist.cpp#104

In PicasaWeb tool, you already play with digiKam DB TagsPath properties when items are imported from picasa to digiKam :

http://lxr.kde.org/source/extragear/graphics/kipi-plugins/picasawebexport/picasawebwindow.cpp#947

In this case, you set TagsPath to DB of course.

We can export or import more image properties to expand QMap contents. It's easy and do not depand of kipi host application as well. Gwenview for ex ignore this stuff...

Gilles

SVN commit 1115757 by jmueller:

Added option on how to export tag paths, look at:
http://www.flickr.com/photos/47251968@N04/4527472537/

BUGS: 234099

 M  +3 -3      picasawebtalker.cpp  
 M  +25 -1     picasawebwidget.cpp  
 M  +8 -0      picasawebwidget.h  
 M  +54 -39    picasawebwindow.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1115757

thanks