[Digikam-devel] [digikam] [Bug 339342] New: Scanning for new items does not recognize modified tags in sidecar files

[sms.paul.v.l at gmail.com]

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

            Bug ID: 339342
           Summary: Scanning for new items does not recognize modified
                    tags in sidecar files
           Product: digikam
           Version: unspecified
          Platform: Mint (Debian based)
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Sidecar Management
          Assignee: digikam-devel at kde.org
          Reporter: sms.paul.v.l at gmail.com

Situation for 1 possible 2 problems: 
1) Two separate computers with digikam installed each with their own local
database "/user/someuser/digikam"  "Mint Debian systems, identical versions".  
2) Both systems share a common usb drive loaded with camera raw and jpg images
"~25,000 images at ~340 gig "
3) usb drive is mount to both machines at /pvl/someyear so it looks the same to
both digikam installs and more importantly to me.
Problem:
1) Changes made on one computer to image tags updated to the usb drive are not
found by digikams initial start up on the second machine.
2) Deleted tags are not updated except through maintenance and are also not
updated on the second machines initial start up.
3) Changing one tag for one image out of 25,000 requires me to run maintenance
on all 25,000 images taking hours.  This i see as a problem. 

Reproducible: Always

Steps to Reproduce:
1.Take one image assign it any tag update to sidecar only on first machine "usb
drive".
2.take usb to 2nd machine and add to collection, then modify image add a second
tag and update
3.return to first machine let it scan for new items check if tag modification
shows on first machine


Actual Results:  
Returning to the first machine will see no change in tags modified in the
second machine

Expected Results:  
I would expect that there is a time stamp for tags and sidecars "also absolute
and relative file location" that will allow the "start up scan" to catch
modified sidecars along with newly entered images.  This would also change the
maintenance cycle time dramatically.  

There is no Severity option I could find.
This is a great program that is almost unusable because of how tags are
maintained.
Even if I used only one computer and one data base moving a small number of
files in a large collection with multiple folders is problematic.

-- 
You are receiving this mail because:
You are the assignee for the bug.