I started f-spot importing around 9,000 of my photos. Let's say all my photos are stored in subdirectories under /media/shared/photos called 2008, 2009, 2010 etc.
I left it going overnight and F-spot ground to a halt just over two thirds through and quit.
I opened F-spot up the next morning and noticed that it had got up to "2006". I chose to import the photos directory again, and it did the remainder of the subdirectories.
So all the photos are in now, but the problem is that F-spot has done something weird with the directory structure when I looks use the "Folders" tab. So, reflecting the two import sessions, I have one directory structure like this:
/media/shared/photos/...(year subdirectories from 2002 to 2006)
/media/shared/photos/...(year subdirectories from 2006 to 2010)
Rather than one combined
/media/shared/photos/...(year subdirectories from 2002 to 2010)
Hopefully the attached screenshot will help explain what I mean.
Is this expected behaviour, or should it be a bit more intelligent than this and combine the source directories into a unified file structure?
Binary package hint: f-spot
I started f-spot importing around 9,000 of my photos. Let's say all my photos are stored in subdirectories under /media/ shared/ photos called 2008, 2009, 2010 etc.
I left it going overnight and F-spot ground to a halt just over two thirds through and quit.
I opened F-spot up the next morning and noticed that it had got up to "2006". I chose to import the photos directory again, and it did the remainder of the subdirectories.
So all the photos are in now, but the problem is that F-spot has done something weird with the directory structure when I looks use the "Folders" tab. So, reflecting the two import sessions, I have one directory structure like this:
/media/ shared/ photos/ ...(year subdirectories from 2002 to 2006) shared/ photos/ ...(year subdirectories from 2006 to 2010)
/media/
Rather than one combined
/media/ shared/ photos/ ...(year subdirectories from 2002 to 2010)
Hopefully the attached screenshot will help explain what I mean.
Is this expected behaviour, or should it be a bit more intelligent than this and combine the source directories into a unified file structure?
Thanks
Nick