Album vs Project vs Folder

I want to create a project that lists images of plants and animals. So I'd presumably have a folder named Animals containing subfolders, like Mammals, which would in turn include the subfolders Cats, Whales, etc.


So I'm trying to get a handle on the difference between projects, albums, folders and smart folders.


Let's say I call my overall project "Life Images." Should I create a new "project" called Life Images? Should Life Images then include two separate "albums" for plants and animals? And would I then create a "folder" (or "smart folder") for Mammals? And can I create a "Cats" folder inside mammals?


Thanks.

MacBook Pro

Posted on Feb 16, 2012 5:49 PM

Reply
5 replies

Feb 16, 2012 7:08 PM in response to Kirby Krieger

Thanks so much for the links. It helps a lot, though I'm still a little confused. One thing you wrote in particular caught my attention:


"The one method I recommend against is using Projects as your major subdivisions."


It sounds like you create Albums inside Projects, so am I correct in assuming that you would use a Folder for your major subdivision?


So let's say I want to get the ball rolling by importing images of members of the cat family. Would one of the following schemes work?


Folder = Life Images


> Project = Animals

>> Album = Mammals

>>> Folder(?) = Carnivores

>>>> Album = Cats


> Project = Plants

>> Album = Flowering Plants


* * * * *


Folder = Life Images

> Folder = Animals

>> Folder = Mammals

>>> Project = Carnivores

>>>> Album = Cats

>>>> Album = Dogs


* * * * *


Also, if I create a system that doesn't work, do I have to start from scratch, or can I change Projects to Albums or Folders and drag images from one to another?


Thanks.

Feb 16, 2012 9:55 PM in response to David Blomstrom

You can move Images between Projects. This is as simple as selecting and dragging. The destination Project must be shown in the Library tab of the Inspector. (You cannot move images by dragging and dropping from one Browser to another.)


"Projects" in Aperture are a unique kind of container. You should understand their "uniqueness" before committing to any storage structure.


You upper scheme doesn't make sense: Albums cannot contain Folders (or other Albums).

It also is not recommended: Projects should (by common consent -- this isn't Apple's official position) contain 1,000 Images or fewer. I limit mine to 500, and mostly range between 15 and 300.


You lower scheme makes sense, except with the same limitation on Projects.


I have several times already recommended treating your storage structure distinct from your retrieval structure. Have you decided to not do that, or has it simply not registered?


You should -- hey, free advice 😉 -- make a detailed, exact, and exhaustive list of _what groupings of images you want to be able to retrieve_ first. Then design a database that allows you to do that. Do the abstract work first, and you won't have to redo the concrete work six times to get it right.


I recognize the excitement of seeing the possibility of your project rising from the shimmering surface of new software. In order to make it work, however, you are going to have to learn a whole new software program. Aperture is broad, deep, and different. Mastering it takes a good bit of time. Set up some sample databases, try things out, work your way through the excellent "Exploring Aperture 3" tutorial (available for the Help menu -- though you might not be able to use the sample Library, as it shipped with the $200 version and not with the $80 version).

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Album vs Project vs Folder

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.