Skip navigation

Workflow and Aperture Project Names

456 Views 2 Replies Latest reply: Jul 29, 2013 10:45 AM by azartguy RSS
azartguy Level 1 Level 1 (0 points)
Currently Being Moderated
Jul 28, 2013 11:15 PM

I don't know is this is do-able but here goes.


I frequently have 30-40 images in group that I import into Aperture3. Some I simply save as is; some I edit one or more versions. If I edit them (usually in Photoshop) it may take several days or more to do a final edit & save versions of 2-3 images. The issue is that in the meantime I'll be adding Projects. I may end up with half a dozen projects that I'm "working" on concurrently mixed in with some "complete" projects.


I would like to separate the "working" from the completed projects.


Color labels apparently don't apply to Projects,  so my old desktop>Pictures >Color Label Folder system doesn't work in Aperture.


I've set up this workflow:  Camera Folder > Aperture >  Date_Camera Folder Name > Import > (rename) Project> DATE_NAME_WORKING .


When I export the file to edit and Save in Photoshop it goes back into the Aperture Library folder with some indecipherable code, e.g., 20130720-193156,  so the questions are:

  • do the Project names that I see in Aperture matter? 
  • can I change the Project name again when I finish editing, delete"working" without creating Library problems down the line?
  • Or, is there another workflow that would handle this?


Thanks for any input, Brian

iPad 2, OS X Mountain Lion (10.8.2)
  • Kirby Krieger Level 6 Level 6 (11,570 points)
    Currently Being Moderated
    Jul 29, 2013 5:50 AM (in response to azartguy)

    Hi Brian.


    There are several good ways to group Projects (I, too, would like to see Project tagging in the next version of Aperture.)

    • Use the built-in "Favorite" designation.  (Click the Action Menu {the gear icon} at the top right of the Library Inspector.  Directions on this page of the User Manual (search for "favorite").
    • Use some kind of text-tag in the Project Name, and then search using either the Library Inspector or the Projects View search.  (Here is a post of Project Naming conventions.)
    • Use some kind of text-tag in the Project Description field.  This is available in the Project Info panel, brought up by clicking the "i" icon in Projects View or, when the Project is selected in the Library Inspector, with the command "WindowÔ××Show Project Info".  Mine is bound to "{Shift}+i".  I put several text-tags in the Project Description.  Most of these are related to the develop status of the Project (e.g.: described, keyworded, developed, done, dropped).  I put these text-tags in using Keyboard Maestro, but any text-replacement program will work (incl. OS X's).  I use, for example, "Not.Keyed", and then (manually) removed the "Not" when the Project's Images have been keyworded.
    • Create Folders in the Library Inspector, and move your Projects.  This is rarely used -- I use it with every Library I administer.  In my professional Library (I'm an artist currently using cameras to record data) I keep two main trunks, each branched into many limbs.  The trucks are, in effect, "Current" and "Archived".


    What you say about exporting to Photoshop and saving worries me.  The standard workflow is to assign (for example) Photoshop as Aperture's External Editor, and then send the Image to the external editor.  When it is closed and saved by the External Editor, it should show up in Aperture as a new Image.  There is a Badge which indicates that the Image was edited externally.  Is there a reason you are using what seems to be a non-standard workflow for editing Images in Photoshop?


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • 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.