document how Shotwell reads/writes tags in photo files
Submitted by Adam Dingle
Assigned to Adam Dingle
Link to original bug (#718577)
Description
---- Reported by adam@yorba.org 2012-05-28 09:16:00 -0700 ----
Original Redmine bug id: 5314
Original URL: http://redmine.yorba.org/issues/5314
Searchable id: yorba-bug-5314
Original author: Adam Dingle
Original description:
A sophisticated user might reasonably want to know which EXIF/IPTC/XMP tags Shotwell reads from and writes to when it stores titles, tags and other information. They might also want to know how Shotwell resolves conflicts when the tags in a photo file aren't the same as in Shotwell's database. Currently we don't document this anywhere. We should either add this information to our Mallard help (e.g. on the "Photo files" page) or add it to our wiki somewhere and link to the wiki from Mallard. (There is a wiki page "Meta tags in other applications" with some of this information today, but its name wouldn't inspire a user seeking this information to look there, and the tables on that page are formatted inscrutably. One possible approach here would be to clean up that page, but if we did so we'd need to elevate the information about Shotwell to a more prominent place.)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 1 year ago
- Status changed from Open to 5
- Assignee changed from Lucas Beeler to Adam Dingle
- Resolution set to fixed
I cleaned up the wiki page so it's formatted nicely again. I think that's good enough for now. Closing.
Comment 2
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:57 UTC ---
This bug was previously known as bug 5314 at http://redmine.yorba.org/show_bug.cgi?id=5314
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.13
Resolution: RESOLVED FIXED