Skip navigation

Importing into Specific Folders

532 Views 6 Replies Latest reply: Feb 12, 2013 6:26 AM by lsb RSS
lsb Level 1 Level 1 (120 points)
Currently Being Moderated
Feb 11, 2013 7:16 AM

Hello,

 

I continue to struggle with Aperture...

 

I have decided to organize my library into yearly folders with smart albums in each folder for individual months.  I can then add/create specific projects to go into the yearly folder when I choose.

 

However, when I now attempt to import, I can't import into the general folder album, which would then disseminate photos into the monthly smart albums.

 

While I can choose the specific folder (2013), the program always wants to import into an untitled project within this folder, which means the photos go in a project, not the smart albums (see images). 

 

I'm sure there must be an easy fix-thoughts?

 

Thanks!

Ps. I'm not importing duplicates all the time-just two photos for this particular import.

lsbScreen Shot 2013-02-11 at 3.03.33 PM.pngScreen Shot 2013-02-11 at 3.04.58 PM.png

iMac, Mac OS X (10.3.x)
  • William Lloyd Level 6 Level 6 (19,220 points)
    Currently Being Moderated
    Feb 11, 2013 7:20 AM (in response to lsb)

    That's because Aperture stores photos in projects.  That's where photos live.  Folders don't hold photos; they hold projects, or smart albums, or other things. But the ONLY thing in Aperture that can actually "hold" photos is a project.

     

    So relying on a big "folder" to store everything won't work.  You could use a big "project" to store everything if you want.  Knowing a bit more about how Aperture works should ease your frustration a bit.  It's fairly flexible, but there are some things which are immutable truths and one of them is "projects contain your photos, and a given photo resides in exactly one project" is a big one.

  • Kirby Krieger Level 6 Level 6 (11,570 points)
    Currently Being Moderated
    Feb 11, 2013 8:29 AM (in response to lsb)

    I think this short guide I wrote may help you.  Aperture is _very_ flexible.  You are two-thirds of the way up the only hurdle. 

  • Kirby Krieger Level 6 Level 6 (11,570 points)
    Currently Being Moderated
    Feb 12, 2013 5:59 AM (in response to lsb)

    Hi,

     

    You can ask as many questions as you like  -- we have no limit on that behavior here.

     

    The User Manual is well done and is always the first resource I search.  There is a page titled

    Dragging Images into Different Projects and Albums

     

    Click the link for the short but thorough instructions, which include this:

    You can drag images into different projects and albums. Depending on where you drag an image, Aperture either moves or copies the image to the new location.

    As a general rule, when you drag an image into a different project, Aperture moves the image into the new project.

     

    Understanding the unique relationship between Images and Projects (and the differences between Projects and Albums) is crucial for a dynamic use of Aperture.

     

    I would add that you might also consider separating your _storage_ containers from your _retrieval_ containers.  For me, for a personal Library, the most sensible storage structure is by shoot and date.  In this scheme, years are Folders, and Projects are at the end of the path.  One advantage of this is that Projects rarely hold more than a few hundred Images -- this is more humanly possible to administer, and allows me to take advantage of the Project Description field and the ability to easily assign Places from the Project Info panel.  (I do create subsets of large Projects using Albums.)

     

    The _retrieval_ structure spans Projects.  So I might have a whole set of Albums devoted to birds, or my grandkids, and so on.

     

    Gotta run.  HTH.

     

    --Kirby.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.