Summary: | HUB : optional finegrained metadata for modified/access/changed time and digiKam last read/write | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | julien.t43+kde |
Component: | Metadata-Hub | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | REOPENED --- | ||
Severity: | wishlist | CC: | alan.pater, caulier.gilles, veaceslav.munteanu90 |
Priority: | NOR | ||
Version: | 2.8.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
julien.t43+kde
2012-11-14 00:36:35 UTC
Not sure when this changed, but digikam 4.8.0 makes use of all the available Date fields. Here is the results from a new blank file passed through digikam: Exif.Image.DateTime Ascii 20 2015:03:06 16:26:47 Exif.Photo.DateTimeOriginal Ascii 20 2015:03:06 16:26:47 Exif.Image.PreviewDateTime Ascii 20 2015:03:06 16:26:47 Iptc.Application2.DateCreated Date 8 2015-03-06 Xmp.xmp.CreateDate XmpText 19 2015-03-06T16:26:47 Xmp.xmp.MetadataDate XmpText 19 2015-03-06T16:26:47 Xmp.xmp.ModifyDate XmpText 19 2015-03-06T16:26:47 Xmp.digiKam.CaptionsDateTimeStamps LangAlt 1 lang="x-default" Xmp.tiff.DateTime XmpText 19 2015-03-06T16:26:47 Xmp.exif.DateTimeOriginal XmpText 19 2015:03:06 16:26:47 Xmp.photoshop.DateCreated XmpText 19 2015-03-06T16:26:47 It looks to me like digikam is now using MWG guidelines. This bug report needs more info. Is the issue fixed? This file is not fixed with current implementation of MetadataHub. The time stamp must be managed as Comment/Ratings/Tags information in Metadata Settings panel. Gilles Caulier This entry is illegible for GSoC 2016 project : https://community.kde.org/GSoC/2016/Ideas#Project:_digiKam_MetadataHub_improvements Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. |