On Mon, Sep 27, 2010 at 2:03 PM, Jim Nelson <[email protected]> wrote: > Hi Kent, > > Importing has some caveats, as you're noticing. > > On Thu, Sep 23, 2010 at 2:08 PM, Kent Tenney <[email protected]> wrote: >> >> I'm trying to figure out Shotwell's world view. >> >> If I choose "copy" when importing, the path of the original is >> lost and replaced with a path based on date. > > It's not really lost, it's just that it's exactly what it sounds like: > Shotwell makes a copy of the file in your XDG Pictures directory (probably > ~/Pictures) and imports that into its library.
Right, but the _path_ of the original seems lost, the files location in the hfs. > >> >> I won't be copying, the path structure has meaning and I >> don't want it discarded. >> > > Then you want to link rather than copy. > >> >> If Shotwell detects a duplicate file it is ignored. >> > > That's correct. > >> >> I can see this makes sense if copying, not so much if linking. >> > > It depends; I think what you're suggesting is that duplicate detection > should only be used to prevent a file copy. There are other import > scenarios, particularly importing from a camera or an SD card. Right, my wife's collection is a nightmare of duplication, however her workflow would prefer copying, and dupe ignoring would be great. > >> >> I would prefer if Shotwell didn't have an opinion on what files to >> ignore, and photo.db represented an accurate representation >> of my collection. Some of my duplicates are mistakes and I'd >> like Shotwell to help me weed, other dupes are for a reason. >> >> Does this sound reasonable? > > It does, but I think I'd like to get a clearer picture of when Shotwell > should use duplicate detection and when it shouldn't I'd rephrase "dupe detection" to "ignore dupes" I guess it would consist of a preference: ignore duplicates when linking: yes/no I would choose "no" I have dupes in my collection which are not mistakes, they are the same file, but live in different contexts. (in your view, at > least), and how it's presented to the user. For example, how would Shotwell > help you weed them out (beyond just showing you the same photo twice or more > in your collection). If I was looking at one of the collection views which included a file which existed in multiple locations, I might expect to see: - multiple stars under the thumb, one for each copy found - a link which would bring up a listbox with absolute filenames - some distinguishing feature, maybe just a different border color If dupes were allowed, a view named "Duplicates" would show thumbs of all files which live in more than one directory. I am very interested in Shotwell's photo.db file. My plan is to scratch some of my particular itches with Python, drawing on the data in photo.db, so I want it to accurately reflect my directory structure. Thanks, Kent > > -- Jim > _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
