Projects vs Albums vs folders

Hi
How do you guys organize your photos?
Im thinking about having 1 project per year and create albums for "events" like trips, birthday parties... you name it
Tell us a little about your organizing workflow!
Thanks

It sounds as though you did not read what I posted at the second of the two links I pasted in for you. I recommend it .
The task you face is to create an +access structure+ for your images.
Your images must be in a container.
You can have as many containers as you like. Almost everyone prefers having more than one.
You can group those containers. Group them so that you can find them more readily. (Remember, you are creating an +access structure+ .)
The +access structure+ can, and imho, should be different from your +output structure+. I suggest that you put your images in one place in order to retrieve them, and that you put virtual copies of the retrieved images in another place when you are preparing them for output.
In Aperture, the container through which you access you images is called a Project. This is, imho, indescribably poorly named -- but the name is a given, and is immutable. No matter what, your images have to go somewhere -- stick them in these containers called "Projects".
Group your "Projects" using Folders.
When you have a project (small "p") for which you will be preparing and outputting images, create an Album. If you have parallel projects (small "p"), use Folders to group them by kind.
You'll end up with two "trees" in your Aperture garden:
. a nested Folder tree of containers which hold your images: those containers are Projects
. a nested Folder tree of containers which your projects (small "p"): those containers are Albums
That's (basically) what I do. Read through the long posts linked above for more.
The number one suggestion I have is to cleanse your mind of the misleading label "Project". Just think of them as bins which hold your images. Make each bin hold a shoot (much like a "roll" -- if you've ever seen those antediluvian strips of sprocketed plastic) and you'll be well on your way to working with Aperture in a way that is simple and smooth.

Similar Messages

Organizing with Folders vs Projects vs Albums vs Stacked Photos

Question - Longtime Apple user, but relatively new to Aperture. Working on organizing a large collection of photographs, and am debating whether to organize by Project and grouping similar Projects into folders, or whether to use Projects as my major subdivisions, and organizing within projects using Albums or Stacks.
I realize that there's probably no right answer, so I'm hoping that anybody reading this note could take a quick minute to share the philosophy they apply to organization, as well as any concrete advantages or drawbacks to Projects, Folders, Albums, or their own method.
Thanks for sharing!
Mark

Projects are, imho, badly misnamed. Aperture was designed with the general plan that one shoot would be one Project. Projects have one salient characteristic (which separates them from other ways of grouping images) -- each Master must be in a Project, and can be in only one Project. Because of the above, you should conceive of Projects as the master (small "m") and enduring holding bin of your shots. I think of them as boxes, or as binders ("binders" implying, somehow, something more long-term than "album").
However you end up organizing your collection in Aperture, the one method I recommend against is using Projects as your major subdivisions. They weren't designed to be used this way, they shouldn't have more than a few hundred Masters in them, and you are likely to outgrow that system of organization.
I stick with "one shoot = one Project". If I have three separate shoots on one card, I import the files in three separate sets, each with the Masters specially re-named, into three separate Projects. I then use folders to organize my Projects. I use Albums for sub-sets of Projects with more than 60 or so images -- I do a lot of my processing by Project, and I find 60 images is about the most I can easily handle at once. I use Albums also for actual projects (small "p") -- e.g.: a series of cards for sale, or work for a client.
All images are keyworded (again, a per-Project task). I use color labels to indicate the level of development of an image. I use stars to indicate the value of an image (rejected, not yet rated, best of stack, worth keeping, among the best in Project, worth publishing, excellent).
Keywords, color labels, ratings, and Project names give me enormous specificity in creating Smart Albums, which I do extensively.
Additionally, I do three things which I think are uncommon.
. I move my Projects according to the status of their development, and
. I separate my intake, storage, and processing areas from my output areas, and
. I never use Folders to organize by date.
I do this because for me Aperture's two overall functions are best treated separately. Those two overall functions are, generally, Intake and Output, or to be more specific, "Import, Develop, and Store" and "Gather for export, Prepare for publication, and Export". The top-level folders in my Library are
. Administration Smart Albums
. Raw (inputs)
. Cold Storage
. To Serve
Admin Smarties includes "5-stars", "Managed Masters older than 45 days", "Masters Missing", "Printed 17x22", "Re-take", and the like.
"Raw" is the top-level of a folder tree which includes "Just Imported", "Described not Stacked", "Stacked not Keyworded", "Keyworded not Picked", and "Picked not filed". I move my Projects into the appropriate folder. Note that this works well in Projects view -- one can drill down to any level of the Library tree and see at a glance which Projects are where.
"Cold Storage" is where I put all fully-processed Projects (and remember, for me "Project" just means "Shoot" -- if you ever used a non-digital camera, same as a box of slides or a sleeve of photos). I organize these as I see fit. I try to put Projects where I think I will look for them. Clients have their own folder(s). Other photographers have their own folders. On the personal side, I have folders for Portraits of friends, Family, Events, Trips, Indoors, Urban outdoors, Rural outdoors, Close-ups, Test shots, etc. Each of these is further subdivided. I have an entire folder sub-branch just for fine art still-lifes.
The last of the top-level folders holds a large sub-set of folders for output. None of these folders have Projects in them (Projects, for me, are +storage containers+, not output containers). I create a folder for each output project (small "p"), and use Albums as needed. In theory, every image that shows in the output side of my Aperture structure should already have been selected ("picked") and optimally developed as an image (the rating and label tell me the status of the image). What is left for me to do is final selection, pre-press, and export.
No where in my Library structure is any accommodation made to date (other than the "one shoot = one Project rule). The is no reason to organize an Aperture Library by date -- date organization is hard-coded into Aperture at both the Project and the Image level. Since it is already hard-coded into Aperture, I prefer to use the Library organization tools to create a storage and output structure which gives me a level of utility on top of date organization.
In general, I keep my Projects view (the Viewer, not the Inspector) grouped by Library folders and sorted by date (most recent first). If I want to view all my shoots (Projects) by date, I simply ungroup them in Project view. If I want to view them by year, I click the "Year" grouping icon. I find Project view, and the built-in grouping options, quite useful.
When I need to view all of my photos in date order I simply use "Photos" view. Note the sophisticated filtering options available using the "Date" and "Calendar" rules. In general, I set Photos view to sort by either "Import Session" or "Date -- Descending". I regularly use List view when in Photos view.
I complete my set-up with specific file-naming and Project-naming conventions. The important thing here is consistency -- set it up right from the get-go, and stick to it rigorously, and you won't have to second-guess your searches or filters.
Hope that helps. It's a lot of overhead -- but I have and take a lot of shots, I work in spurts, and I valued a system which would let me start and stop at nearly any time and always let me know +by structure+ the status of any shot or image or Project or project -- while remaining flexible and expandable.
My example should at least give you some ropes to use as you simultaneously shape and climb your Aperture mountain. I strongly recommend setting up a practice Library using, say, 10% of your images, and using to for a couple of weeks, tweaking it as you go, before "casting it in stone" and importing your entire collection. Aperture is broad and powerful -- take the time to know and understand it, and you will find your use of it immensely rewarding.
Good luck.

About Folders, Projects and Albums

I set up a Folder named "X" that contains a particular Project "Xx". Within that Project there are different Albums "Xxa...z". Clicking on the Folder should give me an overview of all the versions placed in the underlying Project and its Albums. But it does not. Only a few versions appear. I created some New Projects within that particular Folder and imported a number of different files in those new projects. None of the imported files show up when selecting the corresponding Folder. I have other Folders holding more Projects and Albums with no problems at all. What could there be done to resolve that one issue with Folder "X"?

Thank you to respond. There were no errant search criteria in that folder. Meanwhile I resolved the issue by creating a new folder in the root and dragging the projects and albums to it. After that I deleted the folder that turned out to be corrupted (?) I still don't know what went wrong, but the new folder works out fine.

Working with projects and albums in the browser

I have already posted a question about how to find a project or album. If you have TONS of projects and albums how do you find a specific one in the browser? I cannot see any way to sort other than alphabetically and there is no way to search project or album names.
By the same token, and this is my new question, how do you easily display in the viewer all the files in a project? (a project may contain albums with images that are not stored on the root level of that project, so highlighting the project in the browser does not display them). Or similarly, how do you display in the viwer the images contained in several albums? There eseems to be no way to simultaneaously selct albums or projects. You can have several tabs open but not see the images together in the viewer. In fact to make a slide show off all the images in one project you have to create an album and manually put in all the images.
Similarly, there is no way of making a smart album of all the images in a project or determined albums, which would have been a work around for all these issues.....
Am I missing something really obvious????????? It all seems so basic. Even iphoto lets you do these things! HELP, APPLE!!!!!!!!
several Mac OS X (10.4.8)

Hola Francisco,
Aperture is a much more powerful software than iPhoto and it's crucial to understand the way its library works to get the most of its organization capabilities.
Master images can only be placed (physically) inside projects. These are then image containers. An album only has links to images, and this links can go to any project. So even if an album is inside a project it could be displaying images that are not inside that project but somewhere else (if you drag and drop from other project previously).
On the project panel, projects are display in alphabetical order, but you can also use blue folders to organize projects. My project panel is organized as follows:
Project '1. Imports': A project created to automatically recieve all the photos when a card is inserted in my card reader. I use a hot folder with automator for this.
Blue folder '2. Smart Albums': This blue folder has all the smart albums I need to quickly find any image in the library.
Blue folder '3. Work': This folder has all the projects related to my work.
Blue folder '4. Travel': Contains projects of my travel photography divided by country.
Blue folder '5. Portrait': Contains projects of portrait sessions.
Blue folder '6. Social & Events': Contains projects of differents events I shoot.
Project '7. Templates': Contains photoshop templates to create 9 in 1 frames, etcetera.
As you can see I use numbers in front of every name to keep them in the order I want. Then the metadata does the rest, I add keywords to easily find ANY image in seconds, doesn't matter how long I did it.
A Smart album will search inside the whole Library if you create it at 'All images' level, then you can drag it to a folder to organize them if you want.
I'd recommend the book by Ben Long and Orlando Luna, it made me squeeze all the potential of Aperture, way beyond the manual that came with the program.

Storing in projects vs. albums

Hey!
I've been doing an internship for 7 months now and I've been taking pictures like crazy, I'm up to 4200 and counting.
Currently I'm storing all photos in a project called internship and each event (like roadtrips) are in separate albums.
Recently I noticed that aperture is getting kinda slow so I started thinking, could this be because of all 4200 photos being in the same project?
How are you supposed to organize your photos?
You can either do what I do today or you could switch places of projects and albums (so you have one album in the root and many projects), you could also use folders. Which way is preferred?
Thanks
Nicklas

Good advice above.
Ansman wrote:
Currently I'm storing all photos in a project called internship and each event (like roadtrips) are in separate albums.
Instead, let each road trip or perhaps one day's shoot, or morning shoot be an individual Project, aiming for that goal of (a) logical time-based organization and (b) no more than ~500 pix per project I have not personally tried to quantify the impact of Project size on performance.
"Internship" can be a folder with all the relevant projects in it.
Note that an Album is just a collection of pointers to Versions, so Albums can be created and discarded at will, changing nothing and taking up negligible space. Very powerful tool. Albums are often created by searching on Key Words, another very powerful organizing tool in the database of image files.
Recently I noticed that aperture is getting kinda slow...
Aperture is a very demanding application that can slow down for lots of reasons. Hard drives and RAM are the two main reasons that a workflow slows - and they interrelate. Setup changes, workflow changes and/or version changes can also be causative.
HARD DRIVES
Hard drives slow as they fill so keep drives underfilled. No more than ~70% full is a good maximum guideline, but less full is faster. A hard drive 80% full performs more slowly than a 50% full hard drive. Even a hard drive used solely for backup should be not allowed to exceed ~85% full for stability reasons.
The Aperture Library should be on a fast underfilled internal drive. Reference Masters to external drives as needed to keep internal hard drives underfilled. Use Firewire 800 (thunderbolt on 2011 Macs) rather than USB for external drives when possible.
Back up originals on external drives prior to import into Aperture or any other images app. I cannot overstate how important that is, and various manuals, texts, etc. present workflows that skip that critical step. Also back up the Aperture Library using Aperture's Vaults, which are designed for that purpose.
RAM
Your workflow may be running out of RAM and therefore "paging out" to disk. Page outs slow operation a lot and can lead to instability.
You can evaluate whether or not you have adequate RAM by looking at the Page Outs number under System Memory on the Activity Monitor app before starting a work session; recheck after working and if the page outs number (manual calculation of ending page outs number minus starting page outs number) increased significantly during operation your workflow is RAM-starved. Ignore the pie charts and other info in Activity Monitor.
If page outs increase significantly during operation you can add RAM or simply try to run Aperture by itself. Switching from 64-bit operation to 32-bit operation will also make some additional RAM space available.
On my 2006 MBP with its max of 3 GB RAM I always did a restart prior to a heavy Aperture session to clear any memory leaks and make sure no other apps were open. Browsers in particular will often suck RAM Aperture would otherwise be using.
The problem with running a RAM-deficient workflow like I did is that along with slower operation, page outs can reduce overall stability - - and instability always seems to present at the worst times, like in the midst of processing a time-critical project. It does help a lot to keep a really really clean workflow.
If your test of page outs does show that you are paging to disk the speed of your drives and drives connectivity become even more important than normal. The use of solid state drives (SSDs) frequently reduces the impact of inadequate RAM.
OS 10.7 does seem to utilize more RAM than OS 10.6 does, and that makes sense because over time evolving OSs and evolving apps take advantage of evolving hardware.
IMO all Aperture users who can should routinely bump RAM to at least 8 GB. Two good sources of third-party RAM (Apple overprices RAM) are Crucial and OWC http://eshop.macsales.com/.
HTH
-Allen Wicks

Projects and Albums. Could they have been more ambiguous?

Aperture is feature packed and does a great job editing images. What it doesn't do so well is make it clear EXACTLY what the difference between a 'Project' and 'Album' is. Could someone offer a CLEAR explanation as to what exactly a 'Project' is and why one would use it instead of an album or folder? Case in point. I processed about 400 images yesterday. Some were imported into a 'New Project' directly off the CF card. Others were imported as a folder into the 'New Project'. The folder that was imported was brought in as an album by Aperture. The images imported from the CF card itself are all contained in the project AND the folder. I know there is only one copy of each as the album versions are referencing the master file. But, I now want to move the processed images into an album and then export it. Exporting is another topic altogether...
TIA.

Dan Donovan wrote:
A photo can exist in one and only one PROJECT. Conversely, one photo can exist in as many ALBUMS as you like. The previously mentioned playlist analogy for Albums is great. One song can be in many playlists.
I look at Projects as photo shoots. The raw files from each of my photo shoots are kept in their own project. When I see the word Project, I automatically think "photo shoot".
So, where do albums come into the picture? If I shoot an executive portrait session on 7-12-08, I may create an album with just the favorite photos from that shoot. The album is a way to keep a certain group of images easily accessible. Then, what if the client wants to pull together portraits from that shoot and several others? In that case, I can create ANOTHER album with the exact same selects from the 7-12-08 shoot, PLUS images from any other shoot as well. The bottom line is that albums give you the opportunity to have the same photo in many locations.
Folders are a way to organize your projects, albums, websites, books, etc.
Great explanation thanks. But, you had to go and complicate it by mentioning folders...;-).

Aperture advice needed albums vs. folders - Hey leonieDF L@@K here pls!

Looking for some general opinions and/or suggestions on how to best organize Aperture. I want to really streamline my work. Aspiring professional.
Right now I'm trying to decided on what the benifit (if any) to using folders vs. albums is.
I'll use PROJECTS as a MAIN header - for example, Family, Clients, Travel, Shows etc...
Then within those I want to do several subs.... for example:
FAMILY - project name
- any given year 1995 --- album or folder?
--- sub of that would be, Joe surprise party or Christmas Eve.
Since folders are containers that dont hold images, is it too risky to put sub albums or even projects within a folder? For fear of accidentally deleting a folder & with it all the data?
SUMMARY - Any good tips on how to organize with Projects, Albums and Folders would be appreciated.
PS: would love to hear from leonieDF if you see this post.

The naming of the parts
Assembling the parts named
It is a very useful exercise to develop your own Library structure . The second link above details many of my thoughts while I was first putting together Aperture 3 Libraries.
As Léonie has already indicated, your first mapping is commonly proposed, and inverted. Until you are completely adept with Aperture, stick to "one Project = one out-in-the-world shoot". This is how Aperture was designed to work (afaict) -- starting off that way will give you the broadest geography you can cover without crashing into an unanticipated fold in the landscape.
I found it very helpful to understand and utilize the fact that I use the Library for two distinct tasks: storage, and retrieval. (I use the program for Image development, but that is in effect independent of the Library organization.) My solution is to separate these structures, with Projects (organized with Folders) as a filing system for all my Images organized by "shoot", and Albums (organized with Folders) as a filing system for all of my output projects (small "p" projects".
This works well for me, partly because I am a fine art photographer, and my projects (again, small "p") almost always span several shoots. For instance I am preparing an entry for a show of small works on paper. I have created a Folder for this, in which I put an Album holding the 100 or so Images I'm considering entering. These 100 come from at least 30 separate shoots. I will whittle this down to four, mark them as the ones I entered, and leave the Folder in which I can always see which Images I considered, and which ones I selected.
What works for me is unlikely to work for you -- but it should give you some surveyor's marks as you plot and dig your own Library foundation.
Read the linked messages, play around a bit, and post more. There are very few needs that Aperture can't meet.

Projects or Albums??

I have hundreds of photos on my HD neatly filed within aptly named folders all nestled within a folder named "Dititals".
I am about to start using Aperture V2.1.1 and would appreciate some advice, as to should I create a project for each of my 20 or so folders or just for my folder named "Digitals" and have albums for my other folders.
I will require Aperture to keep its projects/albums in sync with my folders on my HD.
I wish also to keep the originals on the HD within "Digitals."
Thank you for any advice which will be gratfully received.
Regards,
Holty.

With "hundreds" of images it really is your choice. If you would like an easy way to do it you can use file-import-folders as project all of the folders under the root location will become albums inside a project. That being said, my preference and recommendations is to use the project containers quite literally in terms of keeping images related to a project within.... well a project. If you keep your projects relatively lightweight and narrow in focus it will make a multi-machine multi-library workflow a bit more efficient for you.
This may help you out in terms of deciding how you may want to go forward.
http://web.mac.com/rwboyer/RBDesign/Blog/Entries/2008/7/15_Apple_Aperture_2.1Organization.html
RB

How to rganize projects in albums

I have a number of projects under Library Albums, one project per day, like events in iphoto. So when trying to organize, creating an album per month, then putting all the projects in a month in to this alum it is not possible - I must be very stupid, how do I do this?
Or should I read aperture = "feel stupid" that is how I read it today
/k

One method is to use Folders. Folders in Aperture contain Projects and Albums (and other Folders), but do not contain images. So create Folders for each month, and drag the Projects for each of that month's days into the appropriate Folder. Then if you want, you can create albums as subsets of each days shots. So your structure could be:
Folder (Month)
..... Project (Day)
..... ..... Album (Subject)
At least, that's how I understand it.

Updating linked projects and Albums

Hi all, I'm new to Aperture. I keep all my photo's on a NAS box and have linked them into Aperture with Import Folders as projects storing files in their current location. Everything seemed great, it didn't fill my HDD up with 1TB of pictures and it kept my folder structure. I though i had it all sorted, but when i add files to the folders on the NAS box they don't get added to the Aperture projects/Albums.
When i try to do another import it just stupidly creates a copy of the projects and albums inside the ones i already have!
Basically is there a way to use Aperture in this way where i don't have to fill my HDD up with my pictures that i already have stored on a NAS box and that i can update when i add new pictures to the NAS box (preferably automatically) without having to delete all the aperture content and add it again?

Dave,
Welcome to the user-supported Aperture discussion group.
When i try to do another import it just stupidly creates a copy of the projects and albums inside the ones i already have!
I might suggest reading the page of the manual before you call it stupid. It works as designed and as documented as far as I can tell.
[http://documentation.apple.com/en/aperture/usermanual/index.html#chapter=4%26se ction=9%26hash=apple_ref:doc:uid:Aperture-UserManual-91292IMP-1056494]
Basically is there a way to use Aperture in this way where i don't have to fill my HDD up with my pictures that i already have stored on a NAS box
Yes, using referenced masters, which I believe you have already done.
that i can update when i add new pictures to the NAS box (preferably automatically) without having to delete all the aperture content and add it again?
Well, yes, but you'll have to change your workflow.
Aperture is not designed to import a whole computer's worth of files and sort out the duplicates every time. It is designed to do that once to initialize your library. After that, you must import individual folders or photos.
You will be in charge of telling Aperture what to import, unless you set up some Hot Folders and folder actions. People do this for tethered shooting all the time. Still, that will be only for a particular folder. There's no way to make Aperture look "next to" what it imported previously and see if there's anything there.
nathan

Albums vs Folders from iPhoto does not show folders on Apple TV

Does anyone have a work around to assist organization of Albums on Apple TV into Folders from iPhoto. We have 12,000 images on iMac organized into 30 Folders within which are 80++ albums. When synced the Apple TV only displays albums, all Folders deleted. The consequence is having to scroll through the 80+ albums when seeking the one album you want to watch. This poor form of organization on Apple TV is really cumbersome and driving us nuts.

Welcome to the  Discussion Forums
The tv can use events as well as albums, although this doesn't resolve the OP's issue, which is simply one of a large number of photo albums. I have a lot of photo albums (without checking, I think I have around 250) and scrolling through them can be challenging.
What I do is to keep albums organised into groups such as 'Holidays', 'Weddings' etc and introduce a specific character at the start of the album title, which indicates which group the album belongs to.
For example ' ☼ Marmaris 2008 ' or ' ♡ Mark and Jasmine's Wedding 1969 '
It doesn't reduce the long list of albums on the tv, but it does help to keep themed albums together in the list and so makes finding the specific album you are looking for much easier.

Can I merge or combine 2 "album artwork" folders? I have saved music onto an external server from 2 computers but the artwork that I have manually imported remains in the default folder in the music/itunes/album artwork folder on the respective PCs. Thx

Can I merge or combine 2 "album artwork" folders? I have saved music onto an external server from 2 computers but the artwork that I have manually imported remains in the default folder in the music/itunes/"album artwork" folder on their respective PCs.
i.e. artwork uploaded on one PC won't apppear on the other PC because it is saved locally...
I'm confident that i won't beable to just merge the 2 because thy'll have the same folder names.
On the same note: can I have iTunes create these files on the external server/Hard drive also so that either computer can use them at the same time?
(like I have my library- can the other files be saved remotely)
Thx

i'm using iTunes 10 BTW

Photo library albums and folders taking up more space

If you create albums and folders on photo library it appears to duplicate the pictures and take up more space. Is there any way to avoid this since you can't group pictures otherwise?

Change your import settings to 128 AAC (assuming that's what you want - I'd choose MP3s, personally, since they will work in other programs and portable devices).
The previous default is AAC encode, High Quality (128kbps)
Then you can just right-click on selections and choose "Create AAC version". It will say "Create MP3 version" if you decide to use thoe import settings.
Of course you already have an AAC version, but itunes will convert it to the lower rates. I just tried it on the free single of the week, "Boarded Doors" and the file size went down from 6.9MB to 3.2MB.
You can choose to convert an album at a time - you don't need to do it song-by-song.
I suppose you could do your entire library in one fell swoop, but frankly with the size of my library, I think itunes would crash at some point. Also my hard drive would fill up. ; )
Note - this makes a COPY and does not replace the original file. So you'll need to delete the originals and make sure they go to the recycle bin.
Still, it's faster than feeding all those CDs in the drive!
So that is another reason for doing one CD at a a time, to make sure the copies get made and that the duplciates get gone.
Message was edited by: Katrina S.

Projects and Albums out of order

It used to be Projects and Albums would line up in alphabetical order when created in Aperture Libraries. It hasbn't been happening for me in recent updates, and I can't find a way to set this in preferences. Even worse, some times albums won't let me change their order — they snap into different order than I drag them in. Don't know what's happening.

When you drag any project or album, Aperture switches to Manual arrangement of all.
Click on the gear icon at the top right of the Library list Sidebar, choose Keep Projects and Albums arranged by, and choose alphabetic if that is what you want. You can't modify by dragging, though.
Ernie

Sorting albums in folders

With iPhoto 11 I use to create folder in the source left panel Album and that I drag the event into the folder. Right clicking on the folder name I can sort the folders, but the events inside the folders aren't sorted. Right click the event name into the folder shows "sort album" but it does anything.
Is there a way to sort events/album inside folders?

Terence,
thanks for the response. I now understand the design constraint.
But here where I ned further guidance.. Not quite there.
1. Create a NEW Album with the high level folder highlighted
2. Select the source images from the LIBRARY-->Photos (now all selected in yellow)
3. Drag and drop these (30+ ) photos into my new Album (ie France under my Holidays folder)
4. I see ALL the photos in the NEW ALBUM ('FRANCE') that were in the folder.
I can goto the ALBUM and select all unwanted and CUT them out from the folder, but my questions is
How do I create a NEW ALBUM and have nothing in it.. When I drop photos into this ALBUM, I see everything else from the folder level in it as well..
Is this due to what I have currently selected (ie the folder, when I create the NEW ALBUM)..??
Almost there !!
Regards
Ray
(Melbourne Australia)

Projects vs Albums vs folders

Similar Messages

Maybe you are looking for