Um ... the complete-and-total-and-instant indexing of all index-able data has made hierarchical filing an un-necessary art.
We used hierarchical filing systems as storage structures with a built-in retrieval structure. This made good sense and worked well for physical records. We are, in ways we are not aware of, completely trained in this kind of taxonomy.
Physical records exist in one and only one place at a time. If you wanted the Beaverman contract from 1954, you knew it was with the 1954 files, under whatever scheme the office was using that year ("File by date!", "No! File by customer!", "No No No! File by customer; archive by date!"), and any lackey could find it (assuming it had been filed correctly).
Our data is no longer physical. Our records now can be presented and modified from multiple places at multiple times.
Filing itself is actually a waste of effort with electronic records.
Our records now are _tagged_ with metadata, and the data that makes up the records (e.g.: text — but could be, for example, average hue, or presence of a specific level of pixel saturation) is itself used to _classify_ our records.
In place of filing, we use what I think should be called "retrieval schemes".
Retrieval schemes are made up of retrieval containers. Retrieval containers show you their contents.
There are two types: manual, and automatic.
Manual retrieval containers hold representations of whatever you put in them.
Automatic retrieval containers hold representations of the results of _searches_ that are executed when you select them.
In Aperture, manual retrieval containers are Albums. Automatic retrieval containers are Smart Albums.
The structure of your Library is yours to make and change. I recommend a few general practices.
• Every shoot is a Project. Projects are your long-term, permanent, _storage containers_.
• Develop your own keyword list that is meaningful to you. Keywords are for you to find your Images. (Advanced: do use a hierarchical keyword list. But that is, as stated, advanced.)
• Set up three separate "branches" in your Library: a storage branch (containing Projects), a retrieval branch (containing often used global Smart Albums), and an output branch (containing publishing projects — e.g.: a wedding album, specific vacation slideshows, etc.). ("All pictures of your grand-daughter" is a retrieval container, and will be a Smart Album. "Twelve pictures of your grand-daughter that you used for the 2004 family calendar" is an output container, and should be an Album containing, at first, the 22 pictures you selected initially from your retrieval container.)
• Do not organize _any_ branch by date. Date is hard-wired in your Images; date-retrieval and date-sorting are hard-wired in Aperture. You can _always_ sort Images and Projects and your Library Folders by the dates of the Images in the containers.
• Use Places. If the files you import do not have location data, add it to the Projects/Shoots after every import (specifying location data for a Project specifies it for every Image in the Project).
• Set up and rigorously use a Project-naming convention. Since Projects are your long-term storage containers, label them with helpful, descriptive. information. Keep in mind that you may want to search for Projects/Shoots, and not for Images. The only way to search for Projects in Aperture is a text search of the Project Name and the Project Description. (The Project Description shows in the Project Info dialog.) For example, you may want to search for all your vacation shoots. You would want to include some text in the Project Name (or the Project Description) that is unique to those Projects. (I use "Travel:".)
• Make as many containers as are useful. Save as few as possible. It is often less work to recreate a container than it is to find it in a long list.
In short:
Stop filing. Wisely name and tag. Create retrieval containers as needed. Make things. Save in an output container each collection of Images for each thing you made.
HTH,
—Kirby.