[Bug 190055] New: Ability to apply metadata changes to multiple pictures at once

[Gilles Caulier-4]

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





--- Comment #20 from Gilles Caulier <caulier gilles gmail com>  2009-07-10 00:03:28 ---
SVN commit 994015 by cgilles:

Metadata Template : Added IPTC subjects Codes support.
CCBUGS: 190055


 M  +3 -0      database/imageinfo.cpp  
 M  +6 -0      dmetadata/dmetadata.cpp  
 M  +30 -14    dmetadata/template.cpp  
 M  +9 -3      dmetadata/template.h  
 M  +13 -33    template/iptcsubject.cpp  
 M  +1 -4      template/iptcsubject.h  
 M  +26 -0     template/templatemanager.cpp  
 M  +24 -0     template/templatepanel.cpp  
 M  +2 -1      template/templatepanel.h  
 M  +14 -0     template/templateviewer.cpp  


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

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #21 from Gilles Caulier <caulier gilles gmail com>  2009-07-10 00:15:57 ---
New screenshot, with IPTC Subjects code support :

http://farm3.static.flickr.com/2515/3704796021_7cde8fe0a3_o.png

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Michal Thoma]

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


Michal Thoma <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #22 from Michal Thoma <michal thoma cz>  2009-07-10 19:09:56 ---
Will it be possible to change these metadata filelds directly from the right
sidebar or it will be needed to dial template dialog, create template and then
apply metadata (as it's now in 1.0b2)?

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #23 from Gilles Caulier <caulier gilles gmail com>  2009-07-10 19:14:38 ---
>Will it be possible to change these metadata filelds directly from the right
>sidebar

not yet. it's a viewer for the moment.

But metadataedit kipi-plugins still there. You can edit all field like you
want, but not in batch.

>or it will be needed to dial template dialog, create template and then
>apply metadata (as it's now in 1.0b2)?

yes. making template is perfect for workflow. you create a set of templates for
different situations. The advantage is to be able to batch template in batch
queue manager.

Gilles Caulier

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Michal Thoma]

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





--- Comment #24 from Michal Thoma <michal thoma cz>  2009-07-10 19:49:25 ---
(In reply to comment #23)
> >Will it be possible to change these metadata filelds directly from the right
> >sidebar
>
> not yet. it's a viewer for the moment.

I'm quite happy for that "not yet".

>
> But metadataedit kipi-plugins still there. You can edit all field like you
> want, but not in batch.

One image at time is too limiting.

>
> >or it will be needed to dial template dialog, create template and then
> >apply metadata (as it's now in 1.0b2)?
>
> yes. making template is perfect for workflow. you create a set of templates for
> different situations. The advantage is to be able to batch template in batch
> queue manager.

I agree, especially when the "Rights" set of fields is concerned. These repeats
in patterns and here the templates are logical and very beneficial approach.

Though the "Location" datas don't appear repeatedly in such patterns as
"Rights" and there are extremely too much of variants of
country>city>province>sublocation possible. I can hardly imagine to create
template for every place I go to take photographs. While there are  some cases
when photographer goes again and again to the same places I suppose more often
the photographer - once he is satisfied with the job he made on one place -
goes to another new spot to snap what's there. And that's why the palces don't
repat so much as author do...

Anyway if the editing from sidebar is on the development radar, I think I can
live some time with extra clicks to dial and apply templates just for one use
only...

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Michal Thoma]

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





--- Comment #25 from Michal Thoma <michal thoma cz>  2009-07-26 22:44:48 ---
I tried new metadata templates in beta3 release and I have trouble with that.
The applying the template actually affects even these fields which are not set
in the template. So for example if I want to apply my Rights and Contact
metadatas for all my images, I will erase all Location informations which I was
building for years! This I find totally unacceptable.

There should be some checkbox in templates which will allow to set which
metadata field will be subject to change when applying template. Otherwise
there is litte use for the function and even more it poses great risk of data
loss.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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





--- Comment #26 from Gilles Caulier <caulier gilles gmail com>  2009-07-27 06:40:37 ---
I'm agree to add checkbox on each option from template. Photoshop has the same
feature.

Marcel, this make the puzzle a little bit complex to compare template from
image and database in metadatahub. Typicaly, in comparison operator:


http://lxr.kde.org/source/extragear/graphics/digikam/libs/dmetadata/template.cpp#46

... i see 2 solutions :

1/ using boolean operator as well.
2/ check string and stringlist for null.

What's the best way for you ?

Gilles

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #27 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-07-27 17:23:52 ---
I am not quite sure what you mean with "boolean operator".

Generally, to solve this like for comment and tags, I think metadatahub should
store the status (invalid, available, disjoint) for each field of the template.
(That's how it's done for tags: Status is individual for each single tag). Only
fields with status "available" are written. Fields are "available" if they have
been identical for all loaded images or when the user edits them. In the
example above, the status for "location" fields is "disjoint" and they wont be
written.

For implementation, we can use MetadataHubPriv::loadSingleValue for each single
field of the template instead of the template as a whole.
When passing to DMetadata and the database classes for writing, it would come
handy to have a "TemplateMask" class specifying which values to write. Maybe a
class having a bool value for each Template member variable.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #28 from Mikolaj Machowski <mikmach wp pl>  2009-07-28 00:31:15 ---
One checkbox isn't enough to give full flexibility.
Personally I would like system like this:

if template field is empty
:if metadata field doesnt exist
::do nothing, even don't create those field
:if metadata field exist and is empty
::do nothing
:if metadata field exist and is not empty
::do nothing
if template field is not empty
:if metadata field doesnt exist
::create field and fill it
:if metadata field exist and is empty
::fill this field
:if metadata field exists and is not empty
::if use "Apply"[*] action
:::replace contents of metadata field with template
::if use "Add"[*] action
:::ignore this field (existing metadata overcomes template metadata)
::if use "Append"[*] action
:::add content of template field after existing content

[*] In all other cases behavior of these three buttons is the same. Note: those
buttons would be in Caption->Information panel, not templates configuration
dialog. In this way one template could be used in various ways.

This doesn't give full flexibility - this can be only achieved by adding menu
after each template field dropdown menu with choices like: Ignore, Replace, Add
after, Insert before which could considerably increase complexity of interface.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

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





--- Comment #29 from Marcel Wiesweg <marcel wiesweg gmx de>  2009-07-28 11:46:28 ---
Mik, which field in Template is suitable for "Append"? I would imagine that the
copyright fields and the location info is "atomic" in that you either keep it
or replace it.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

> Mik, which field in Template is suitable for "Append"? I would
> imagine that the copyright fields and the location info is "atomic" in that
> you either keep it or replace it.

Sorry, I was bit too fast: this could be used mostly for
captions/titles/headlines and this type of metadata (FotoStation influence).

But it could be used for copyright strings, usage restrictions, instructions.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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





--- Comment #30 from Mikolaj Machowski <mikmach wp pl>  2009-07-28 19:32:17 ---
> Mik, which field in Template is suitable for "Append"? I would
> imagine that the copyright fields and the location info is "atomic" in that
> you either keep it or replace it.

Sorry, I was bit too fast: this could be used mostly for
captions/titles/headlines and this type of metadata (FotoStation influence).

But it could be used for copyright strings, usage restrictions, instructions.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

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


Russell Harrison <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]




--- Comment #31 from Russell Harrison <rharrison fedoraproject org>  2010-01-05 03:37:10 ---
(In reply to comment #25)
> The applying the template actually affects even these fields which are not set
> in the template. So for example if I want to apply my Rights and Contact
> metadatas for all my images, I will erase all Location informations which I was
> building for years! This I find totally unacceptable.
>
> There should be some checkbox in templates which will allow to set which
> metadata field will be subject to change when applying template. Otherwise
> there is litte use for the function and even more it poses great risk of data
> loss.

I would like to second this point.  I had expected to create a template for
rights / contact information and others for common locations as an example.  I
could then apply the rights template on import and then apply location
templates as I review my photos.  What I found was that my rights information
was removed when I applied a location template.

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gus Gustafson]

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


Gus Gustafson <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email],
                   |                            |[hidden email]




--- Comment #32 from Gus Gustafson <efelthauser gmail com>  2012-01-25 18:03:17 ---
It is silly to use templates just to apply something like 'city' to multiple
photos at once. What if I manage photos from thousands of cities? I will need
thousands of templates? (Yes, I would have to keep all templates, in case, for
example, I ever change all the copyright restriction verbiage, etc.) Not a good
way.

The Solution: The right-hand caption/tag sidebar's 'information' tab can be an
editor, not just a viewer. Or An Alternative: the kipi metadata editor window
has an "apply to all selected images" button option.

Second, it is very bad that template fields that are not used in a template
will overwrite pre-existing metadata. Not an intuitive/expected behavior. I
feel sorry for someone who unwarily uses a template to set copyright info, only
to find that many hours of work on location metadata is *lost* (perhaps
*forever* if they have no other memory/record of where each photo was taken).

The Solution: Add Check-boxes next to all fields in templates. The
"Apply-template" action then only changes a field if it is Checked in template.
(The Kipi metadata editor already has Check-boxes...why not also the template
editor?)

In my opinion, these are big problems. I offer my sincere thanks to Gilles and
all others who work on Digikam for your great work. But, I really believe this
needs to be a top priority to improve. These suggested changes would not even
change the GUI much, but even if they did, any user who is bothering to work on
metadata will prefer useability and efficiency over aesthetics of, and
complexity of, the GUI. I am a person who actually enjoys making donations to
software projects that I use a lot. But I do not use Digikam anymore because of
these two reasons. I wish I could, as it is so good in other ways...

--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

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

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #33 from Gilles Caulier <[hidden email]> ---


*** This bug has been marked as a duplicate of bug 144858 ***

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[bugzilla_noreply]

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

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|BatchQueueManager           |BatchQueueManager-Tool-Meta
                   |                            |data

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel