Originally posted by cprobertson1 What sort of organisation do people generally use for their folders and files in darktable?
My archives are starting to get bulky - just now I do a "dump" from the camera/SD card to a folder, and then I import all of that into Darktable - go through and tag all the non-keepers for deletion, and then tag the rest of them by genre.
I suspect I'm not using the full power that darktable has to offer - so I was wondering, from-camera-to-darktable, what sort of organisation and import process do folks like to use?
I have two folder hierarchies - which likely could be three, but the point is they are disjunct, i.e. a set of pictures clearly belongs to one or the other, not both. One is for family photos, one for everything else.
Both follow a shallow yyyy/yyyy-mm-dd_event--or-content/ structure, sometimes subdivided below into days, sometimes with a subfolder for panos or focus/exposure stacks.
BEFORE they go there, or even anywhere in darktable, I use FastRawViewer for culling, with a global 'rejected' folder, which I clean out from time to time. Once move into the structure above, I try to avoid moving files. The reason is that the hierarchy is accessed by multiple tools (and users) in addition to darktable, and e.g. good ol' Picasa would think that the moved file is a new one. Tagging id sparse, by content - e.g. a hierarchy of bee diseases for documentary shots taken for my wife.
Because the photo library used to be managed by Picasa, dates are still the last day of an event, because Picasa auto-created a folder with the current data on import. Consistency is important when you try to find something later.
FastRawViewer, which I now use under Wine in Linux, at basically full speed, is excellent for weeding out generally acceptable pictures, not so much for A/B style 'which one do I keep' decisions. I make those now in darktable, used to be geeqie.