After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582426 - Importing from Camera doesn't place photos in proper heirarchy
Importing from Camera doesn't place photos in proper heirarchy
Status: RESOLVED DUPLICATE of bug 579340
Product: f-spot
Classification: Other
Component: Import
0.5.x
Other All
: Normal normal
: ---
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-13 03:39 UTC by Justin J Stark
Modified: 2009-05-13 17:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Justin J Stark 2009-05-13 03:39:27 UTC
Please describe the problem:
I am using 0.5.0.3-1ubuntu6.  When importing from camera, it asks for a target directory.  There are a few problems:

1) The target directory doesn't default to the default import folder specified in preferences as it should.
2) Photos imported from a camera are not arranged in a YYYY/MM/DD structure.  Even if I select the default target directory as the default import folder, the photos get imported flatly into the directory.  (ie: /Photos/img0001.jpg /Photos/img0002.jpg)

Steps to reproduce:
1. Open the import photos dialog
2. Select a camera
3. Choose a target directory
4. Import the photos


Actual results:
The photos get importing into the target directory in a flat format (even when choosing the target directory as the default import directory).  Ex:
/Media/Photos/img0001.jpg
/Media/Photos/img0002.jpg
etc

Expected results:
Imported photos (at least those imported to the default import directory) should be placed in a heirarchical structure such as those imported straight from a directory.

Does this happen every time?
Only when importing from a camera which is inconsistent with importing from a folder.

Other information:
A checkbox in the import dialog whether to use the YYYY/MM/DD structure when importing is called for while still allowing a user to choose a target directory.

Another alternative would be to use the heirarchy when importing to the default import directory but importing flatly when choosing an alternative directory.
Comment 1 Maxxer 2009-05-13 17:47:01 UTC

*** This bug has been marked as a duplicate of 579340 ***