Bug 292801 - template with unused fields pro-actively overwriting existing fields
Summary: template with unused fields pro-actively overwriting existing fields
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Template (show other bugs)
Version: 2.5.0
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-29 16:10 UTC by Gus Gustafson
Modified: 2023-04-05 14:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gus Gustafson 2012-01-29 16:10:10 UTC
I see that, because it causes loss of data, this qualifies as critical.
Try this: on an image, set a template that does not have the origin city field set. then, use kipi metedata XMP editor to set origin City. check that city is now updated using metadata viewer. then, modify the caption of the image. you will see that the city you set is now erased. this is caused by the template.


Sorry to clone an existing open bug, but I see no way to update the severity and version on the existing bug.

+++ This bug was initially created as a clone of Bug #231114 +++

Version:           1.0.0 (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

Not sure if this is a bug or change request.

I use the metadata template to automatically fill a couple fields. However, I do not use the template for setting the location fields, such as sublocation, city, etc. In other words, those ones are left blank in the template.

However, I recently found that, after applying the template to a folder of images, this caused all the data in those location fields to be deleted.

I think that if there is already data in a field, when you apply a template, that data should not be touched unless the template has something different for that field.  It is better to leave more information, which can always be deleted later, than to delete information unexpectedly (at least, I did not expect to happen.) Or, perhaps the best way is to allow user to choose, for each field in template with null value, whether existing data will be removed. So, maybe each field has a checkbox (that appears or becomes active when null value is present) that you can check to "clear existing data?" or something.

Or, you can forget the checkbox and just let people clear fields on multiple files once the sidebar metadata-edit feature (for fields other than comment) is added, if that is something they need to do.

But I think it is bad to leave it deleting data.

Thanks for a great software.
Comment 1 caulier.gilles 2012-01-29 22:11:53 UTC

*** This bug has been marked as a duplicate of bug 231114 ***
Comment 2 caulier.gilles 2023-04-05 14:44:24 UTC
Fixed with #231114