Dne úterý 07 říjen 2008 Sébastien Barthélemy napsal(a): > Sorry for the first post, it was a bad keystroke > > > This is my proposal for metadata handling. > > > > Requirements: > > - metadata go with the image, preferably in the image > > - no data loss, no legacy data loss > > - automatically migrate legacy data to XMP > > - XMP sidecar can override exif values stored in unwritable raw file > > - cooperation with metadata editors that don't support XMP > > - preserve originals > > - handle photos on read-only filesystems reasonably well > > just giving my point of view on this matter. I think modifying picture > metadata is a tricky topic, and one has to decide what geekie will be: > - a picture viewer > - a picture editor ? > - a picture metadata editor ? (eg: fix the date in the picture exif) > - a picture collection manager (with sorting/classification > capabilities...) > > in the first case, all operation should be read only (or explicitly > warn the user). > > The second and the third are not that different : I would tend to consider > a change of the exif date or orientation as a modification of the picture.
Well, IMO Geeqie should be the interactive part of photo collection management workflow. Other parts of the workflow are ufraw, gimp, ImageMagick, exiftool, hugin etc., everything connected by scripts that define the workflow logic. IMO this is the only setup that is flexible enough to follow the recent development of the Linux photography. The main Geeqie task in the workflow is to select pictures and do something with them, typically pass them to some editor or script. Using keywords and comments is just one method of selecting the pictures. The metadata should be stored in the files because interoperability with other applications is mandatory. XMP is ideal technology for this. The features below should be possible to add, but as the workflow scripts, not in Geeqie itself. Vladimir > > At last, I would expect the following features from a picture > manager,(with decreasing priority): > - let people organize their files as they want > - a clear policy regarding picture modification, such as: " we never > modify a picture without asking", "we never modify a picture at all" or "we > never modify without creating a new revision" > - real picture versioning (based on rcs, svn or so) > - multiple version picture handling: RAW+JPEG and duplicate detection > (one could keep a checksum of all the revisions in order to find > duplicates against old revisions too) > - picture classification (user tags + timeline) > - offline support (keep a local low resolution version ?) > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
