[Digikam-devel] [Bug 140202] Allow fuzzy dates for photos and albums

Brian Remedios brianremedios at gmail.com
Wed Jul 4 18:17:56 BST 2007

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

------- Additional Comments From brianremedios gmail com  2007-07-04 19:17 -------
I'm doing the same archiving of family photos and the dating issue plagues me as well. 

Rather than specify start/end dates I would suggest that we follow the scientific community's approach by specifying an uncertainty factor. I.e. for a number this might be like 10 +/- 0.5.  For date values we would have June 4, 1974 +/- 2 months. Of course this would mean that the specified date would have to be the median date so that the fuzzy date boundary can exist before & after it.

If we add two new integer fields to albums, uncertaintyCount (1-n) and uncertaintyUnit (enum of day/month/yr/decade/etc) we can generate hidden begin/end dates in the DB that can be used for SQL queries.

I'm not familiar enough with the current DB schema to know if we can associate these new values with individual photos but it would be a good addition if we could. They wouldn't be stored as EXIF values, just held by digikam alone.

More information about the Digikam-devel mailing list