Import with "Copy to Library" after "Import in Place" should copy photos to library directory
Submitted by Lucas Beeler
Link to original bug (#718023)
Description
---- Reported by lucas@yorba.org 2011-08-25 15:04:00 -0700 ----
Original Redmine bug id: 4023
Original URL: http://redmine.yorba.org/issues/4023
Searchable id: yorba-bug-4023
Original author: Lucas Beeler
Original description:
From Ian Molton on the Shotwell mailing list on Friday, July 1, 2011:
If one imports "in place" a batch of photos (easily done by accident due
to the (IMO insane) placement of the 'import in place' button that has
no 'saftey' "are you sure you want to be this insane" type option), and
then subsequently try to fix this by importing using 'copy to library',
shotwell (correctly) identifies the images as duplicates, and doesnt
import them.
After reading Ian's comments I've decided that I agree with him. Shotwell's import behavior now is counterintuitive, and could lead to data loss. So I suggest we do the following:
If a user imports a batch of photos "in place" and then subsequently imports the same batch of photos in a "copy to library" import, we should copy the photo files into the library directory and report this to the user.
Related issues:
- related to shotwell - Feature #3126 (closed): Log duplicates when importing (Fixed) duplicates shotwell - Feature #3487 (closed): More sophisticated, configurable handling of duplicates (Open)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:46:00 -0700 ----
History
Comment 1
Updated by Jim Nelson about 2 years ago
- Description updated (diff)
-
Target version deleted (
<strike>
_0.12_</strike>
)
Comment 2
Updated by Jim Nelson 11 months ago
- Target version set to 0.14.0
Comment 3
Updated by Jim Nelson 11 months ago
- Category set to import
Comment 4
Updated by Jim Nelson 10 months ago
- Status changed from Open to 5
- Resolution set to duplicate
This isn't as bad as it once was -- Shotwell doesn't report that it imported the file, rather it reports that the duplicate was not imported. I feel this ticket is a subset of #3487 (closed), which would allow the user to specify how duplicates are handled, and #3126 (closed), which will give the user a better idea of what was imported and what was not, and why.
Comment 5
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Duplicate
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4023 at http://redmine.yorba.org/show_bug.cgi?id=4023
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.14.0
Resolution: RESOLVED DUPLICATE