Please, ignore my last post - that has been corrupted by Apple Maintainance work striking and killing the editor while I was still editing - not for the first time.😠 Perhaps I should move back to silicon valley or adjust my internal clock to California time...
-----
Frank, perhaps a compromise between Kirby's and your storage scheme? Both of your schemes have their strong points.
Usually you will retrieve images using searches, albums, or smart albums and not worry about projects. However, with my workflow, I find myself quite often trying to locate projects, and not only images, and Aperture offers only a poor support to find projects. You can search for them only indirectly by searching images inside the projects and thus hiding other projects.
Browsing your library to track down a particulare project can be tedious, because you have to traverse a tree structure by expanding and collapsing folders. Your folders are the nodes of a tree structure, the projects are the leaves. The problem is, while you are navigating the tree down from the root to the leafs, searching the projects, you will only see the current folders/nodes you are expanding and have to guess which of these folders will contain the project you are looking for. It is a problem very similar to navigating the tree of menu items in a user interface. That is why I found the following guidelines helpful - at least for my kind of library and workflow:
- The top level folders should be set up to collaps or reveal huge portions of your library with one click.
- The names of the intermediate folders should tell you easily at a glance which folder to click next, when you are diving down into a nested structure of folders, so that you do not have to open all of them, if you are looking for a particular project.
It is up to you to decide, which naming scheme will serve you best to navigate quickly to a particular project and to identify it in your library tree.
I name my folders based on criteria that I can remember best. I usually know if I have travelled somewhere before or after a certain other event, and that is why I like to have a chronological structure in the folder names. But my memory for absolute dates is very bad, if I would need to know by heart the exact year and month of a certain shoot to identify the project it would be difficult for me. The date alone as a folder name would not help me much. So the locations or events are part of the folder names too - my projects are anchored in the space/time continuum. And I know the camera I used - if the project contains scans of paper prints or slides, or digital images.
Here is my library structure: a compromise between media kind, event, chronological order and thematic, location based events. One click can collaps or expand all scans of paper prints or transparencies, or reveal all digital images, one click can expand all sailing trips, biking tours, or family pictures, the vacation pictures are grouped chronologically.
This is my private Aperture library, the library I use at work is very different, the work library is structured solely according to tasks: lectures and research projects, because I do not import shoots into that library, it contains computer graphics, satellite data, and derived products.
This structure is perfect for me, because for my workflow I need to access the folders as well as the images, for quite a few smart albums are directly attached to their corresponding projects, e.g. a screensaver album or a selection for a web gallery showing my wildlife pictures from Tanzania or the Galapagos islands will be defined locally and not globally.
And please excuse the screen shot in german - I did not want to rename my folders to english names just for a screen shot.
Cheers
Léonie