Bug 144858

Summary: Add a new BQM tool to allow batch metadata editing
Product: [Applications] digikam Reporter: yuri <yurivr>
Component: Plugin-Bqm-WishForNewToolsAssignee: Digikam Developers <digikam-bugs-null>
Status: CONFIRMED ---    
Severity: wishlist CC: alan.pater, angel_blue_co2004, caulier.gilles, creideiki+kdebugs, jm7, kay, kde.20.micorreo, kdebugs.alex, knizek, mahikeulbody, michau, rharrison, seth.quarrier
Priority: NOR    
Version: 1.0.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description yuri 2007-04-30 07:27:02 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages

When I highlight 30 photos and Image>Metadata>Edit IPTC I have to individually edit details and use the "Forward" key to edit the next one. An "Apply changes to this entry to all entries" key would be super. Same idea with EXIF editing. Oh and one more thing, when using the "Forward" button, it would be nice to have a thumbnail of the photo being edited persistently displayed in the "IPTC edit Metadata" menus. It is hard to keep track which photo is which when they are named in DSC000 etc. format and you have 4000 of them. Thanks, and keep up the amazing work. digikam has already become my primary photo manager and its come a long way.
Comment 1 Xavier Pouyollon 2007-06-18 20:32:49 UTC
Same for me, that would be a great improvement !
Comment 2 Alexander Kluss 2007-08-28 21:32:11 UTC
I tested digiKam today the first time and this was the second test after the start of digiKam. I think this is a basic feature of a meta data editor.
Comment 3 Thomas Schildknecht 2007-10-02 00:50:04 UTC
*** This bug has been confirmed by popular vote. ***
Comment 4 caulier.gilles 2007-10-03 15:40:07 UTC
Hi all,

If you want to batch edit Exif, just follow this way :

1/ Edit metadata like you want from the first picture of the list to batch.
2/ Select all pictures to batch on album, excepted the first one.
2/ Start Image/Metadata/Import Exif menu option from digiKam.
3/ Select the picture than you have just edited metadata (the first one)
4/ plugin said if you want to continue. Said yes of course...

And now all selected pictures have the same Exif metadata... The same way can be used with Iptc.

Gilles Caulier

Comment 5 caulier.gilles 2007-10-03 18:36:15 UTC
*** Bug 144859 has been marked as a duplicate of this bug. ***
Comment 6 Russell Harrison 2009-01-06 15:50:38 UTC
(In reply to comment #4)

Would this overwrite all of the EXIF data including creation time, exposure information, etc. or would it only import information that isn't already set?
Comment 7 caulier.gilles 2009-01-06 16:00:47 UTC
all metadata are overwrited.

Gilles Caulier

Comment 8 Russell Harrison 2009-01-06 18:53:31 UTC
(In reply to comment #7)
> all metadata are overwrited.

OK so this would work well for copying metadata to files produced from the original that you do want all the tags to match but isn't something anyone should do if they only want to change a few tags.  Say artist or copyright for example.
Comment 9 Angel Blue01 2009-03-04 04:11:32 UTC
Would certainly appreciate batch metadata editing in Gwenview 4
Comment 10 Kay Drangmeister 2009-05-20 22:20:38 UTC
I am using digiKam for quite some time now and this is one of the most missing features. I have a current, concrete use case to add:

I have scanned my complete set of negative images via a scanning service. For the "date created" EXIF metadatum, they set the scanning date. They left blank the "date digitized" EXIF metadatum.

So what I like to do:
(a) set the "date digitized" metadatum of 6000 images to, say, 2008-12-20.
(b) since I sorted the images into (dated) albums, for each album (say the 1977-01-12 album has 100 images in it), set the "date created" of these 100 images to, say, 1977-01-12.

User interface would be dead simple: just add an "apply to all selected" button to the EXIF (and others) metadatum dialog. Only the fields modified by the user (this should in many cases be only one) should be modified for all selected images, leaving all other metadatum as they were before.

A "safety" dialog like this would be ideal after clicking the "apply to all selected" button:

  "
  Are you sure you want to change the following for *100* images?
   * date created = 1977-01-12
   * date digitized = 2008-12-20
  "

Thanks very much,
Kay
Comment 11 Michał S. 2009-05-22 10:32:58 UTC
I agree, this is the most needed digiKam's function for me. Setting manually "non-standard" IPTC and XMP metadata in big sets of photographs is very time consuming. Batch mode will be GREAT.
Comment 12 Geoff King 2009-05-22 14:07:14 UTC
I agree with Kay (comment #10).  This would be very useful.  I seem to remember photools on windows having similar functionality to this.  Digital photos generally don't need this type of treatment, but scans always do.
Comment 13 caulier.gilles 2009-05-23 20:52:35 UTC
I plan to do it with digiKam Batch Queue Manager, when time permit...

Gilles Caulier
Comment 14 Milan Knížek 2009-06-13 09:42:59 UTC
Gilles, once you get to batch queue manager & iptc, please consider the various "write" modes: 

(i)   add - if the iptc tag allows repetition (e.g. keywords), add always a new tag and do not touch the existing ones. Otherwise behave as "update".

(ii)  update - if the iptc tag already exists, replace its value with the new one. Do not touch other tags, for which the user has not supplied any value.

(iii) replace/set - delete all iptc data before inserting the new values.

The most useful is probably "add" mode.
Comment 15 Manuel 2009-12-28 20:02:47 UTC
*** Bug 220434 has been marked as a duplicate of this bug. ***
Comment 16 Manuel 2009-12-28 20:05:36 UTC
(In reply to comment #15)
> *** Bug 220434 has been marked as a duplicate of this bug. ***

220434 is very similar, batch copy meta-data from a set of images to another. I did mark as duplicate to concentrate efforts

Later
Manuel
Comment 17 Seth Quarrier 2010-02-17 16:54:07 UTC
As another use case for this, I have a digital SLR camera which records exposure/camera information into the exif tags. However, I have several manual lenses which the camera (Nikon d5000) cannot distinguish between, I would like to be able to batch enter the lens I used to for a group of photos without overwriting the other exposure data that the camera provides.
Comment 18 Johannes Wienke 2010-02-17 16:59:31 UTC
What about using an EasyTag-like editing way? They got a little push button for every input field. If the button is pushed, the change is performed on all selected files. Otherwise it's only performed on the last selected entry only. This could be a bit more logical without the "do things only sometimes" magic proposed in #10.
Comment 19 Alan Pater 2013-12-01 14:06:58 UTC
This would be extremely useful for the project I am involved with, which includes modifying the XMP metadata of > 50K camera trap photos. Some of the metadata is common to all the photos, other to various subsections.
Comment 20 Alan Pater 2013-12-04 12:14:00 UTC
Something along the lines of how Adobe Bridge manages this would be cool. Found a screenshot showing the Append Metadata menu: http://dpbestflow.org/sites/default/files//uploaded_images/metadata/MetadataTemplate.jpg
Comment 21 caulier.gilles 2014-09-01 11:51:45 UTC
*** Bug 190055 has been marked as a duplicate of this bug. ***
Comment 22 jm7@acm.org 2021-09-08 19:48:21 UTC
For an example of how the current code fails.

I have 2180 lines in tags for different geo locations.  about half of these would be distinct sublocations.  Only about half because of the hierarchical structure of the tags.  

I am about to have to move.  If I had used templates (which I didn't as they don't work in a useful way), I would have to modify about 1000 different templates to update my contact information.

What I would like to do is to have a single template that I can set up that is only the contact information and apply that to every single photo in my collection (barring a few that were taken by someone else where I have a partial copyright).
Comment 23 jm7@acm.org 2021-09-08 19:50:54 UTC
Part of the confusion is, I believe that the original developer was thing of templates as an end point rather than a step on the journey.  The template that was applied looks like it is stored in the database somewhere associated with the image as switching images that have had different templates applied selects the template that was last applied to the image.