| Summary: | wish: preview of list of files have metadata to be written | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Cesar Martins <cesar.inacio.martins> |
| Component: | Maintenance-Metadata | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | cesar.inacio.martins, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Microsoft Windows | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
I want to be completely honest, I don't think we'll do it. I don't really see any point in it either. All changes have already been made in the database, so you can see beforehand whether everything is correct. Lazysync has only saved one image ID and thus knows which images from the database must be synchronized to the image file. We have not saved any changes before or after, they should be read again from the image file. Let us assume that you have changed metadata for 1000 images, then we have around 10 changed metadata types, that makes 10000 entries in the list. Do you want to compare all of them based on the file names for correctness? Facial and Geo data based on pure coordinate numbers? Maik Hi Maik, Let me explain my situation here. I'm selecting photos to publish where I need to fill the IPTC title, captions, fix the copyright, fix few tags before. Before committing all this, I would like to review what changes I made and how many pictures will be affected when I click to write all. This will not be a unique situation, probably I will do this frequently. -- Please, help me to understand one situation. Considering the lazy sync. Let's suppose I changed the metadata of 100 files. If I give up to apply theses metadata, I need to click on "Reread metadata from files" right? How do they know which files to reread? Then all changes are discarded, right? -- For better performance and avoid unnecessary I/O reading metadata from files (which is much heavy and slow compared to read a table into the database), should be better to implement a backup/stage table to save all data modified, don't agree? Then you can use this table to manage what was changed and rollback fast. When the user clicks to write all changes, just delete it from the backup table. If they rollback, update the data back and delete it from the staging table. This way you can manage fast what is changed, show it as a report like I'm asking, and improve performance avoid reading metadata from files and writing only when is really necessary. -- About what kind of data to show, I don't think in information like facial, geodata (coordinates), because they aren't readable information. I consider only what into the tab "Caption" and/or basic text fields of EXIF/IPTC/XMP. -- However, I know to implement this isn't trivial, and if isn't acceptable considering the workload and other priorities, that's ok, I understand. -- I see this application as a photo organizer and for that, I'm expecting more efficiency over the usability to make changes. Like the metadata editor, I really consider it very frustrating to use because as a user I need to make a lot of operation (mouse clicks) to change 2 or 3 fields. They should be a screen with a table where you can change fast multiple fields and also should be fast to do in multiple photos. Thanks for your attention! |
SUMMARY When have the metadata option "use lazy synchronization" active, to flush all changed data to the picture files, we need to click on "Album -> Write metadata to file". However, when we made lot of adjustments, we would like to review what will be written and which files and perhaps undo someone or other picture before the flush. -- My request is when clicking in this option, open a review screen with a table showing the list of files with a text showing the changes and a checkbox, to allow us to uncheck to not write that change at that moment. If double click over the picture name, go to the picture (to allow edit the metadata again if needed). Something like : ---- apply| file | field | before | after -------------------------------------------------------------------------- [x] | c:\images\img_1341.jpg | caption| oaks | oaks trees are common in this region | | Title | Tree on the mountain | The biggest Trees | | Tags | trees view mountain | tree mountain landscape --