DT does not recognize ext. changes in XMP
While working on the 7-state-rating patch I stumbled over this bug: DT seems not to recognize external changes in XMP files even though it should.
This issue is at least for the xmp:Rating, I changed it several times, reopened DT, even rebooted but the value shown by DT did not change - it remained the one from the database.
#4 Updated by Tobias Ellinghaus over 8 years ago
- Status changed from Incomplete to Fixed
Since there is no way for dt to know which information is to be kept the one from db or the one from xmp it can't do that. Besides the whole sense of having a db is to not rescan the images/sidecars all the time.
#5 Updated by Simon Spannagel over 8 years ago
Sorry for having this discussion here, maybe we should move to the mailinglist...
Since a file gets a timestamp on altering it it, dt would have to save the time of the last edit and then compare this to the xmp file - take the newer one.
Seriously - how will dt deal with changes of tags/rating added by other dam solutions? If the user forgets to re-import files after using, let's say digikam, and makes changes on the file, maybe something gets lost (or deleted tags are added again).
Isn't it like this? Proof me wrong...
#6 Updated by Tobias Ellinghaus over 8 years ago
In dt XMP files are a means of backup. They can also be used for explicit exchange between applications, but not as a transparent synchronization mechanism.
Following your approach a user could corrupt his xmp files (maybe by digikam or some other software going postal) and loses all his ratings, tags, color labels, history stacks,
Please discuss this on the list (or in IRC).