Skip navigation

Two versions in two different Projects?

2827 Views 45 Replies Latest reply: Nov 13, 2011 12:02 PM by eltjofromu RSS
  • CalxOddity Calculating status...
    Currently Being Moderated
    Nov 4, 2011 12:36 PM (in response to hotwheels 22)


       The Theme approach to organising your images in Aperture appears to suffer a fatal flow in that, as you observe, an image is not necessarily exclusive to a single them.


    This is why Aperture has very powerful keywording and search functions.  Some of my images have a dozen keyword and can be collated with like images on the basis of all or some of those keywords.


    For example:  I take a photo of a kangaroo silhouetted against a sunset whilst at a family barbeque during our summer vacation.  O noes!!! Where to put it?


    Well, it gets placed in my 2011 Summer Vacation Project, and receives keywords of fauna, kangaroo, vacation, family, sunset, Australia, Canberra etc etc.  Which "theme" does it have?  All of them....


    Note also that the reason you may have duplicate masters showing in different Projects is that they were stored in different locations in your Windows machine, and therefore are regarded as unique instances by Aperture.  I had this when I migrated from Windows and had to spend some time reconciling the duplicates.  Mind you, there weren't that many as I spent some time fixing the wordt of it before migrating.

  • Kirby Krieger Level 6 Level 6 (11,550 points)
    Currently Being Moderated
    Nov 4, 2011 1:53 PM (in response to CalxOddity)

    The answer is to use Albums for "themes" -- but Jon has been led to that rich bucket nineteen times by five different guides, and still he paws the ground compulsively, and refuses to drink.

  • CalxOddity Level 3 Level 3 (680 points)
    Currently Being Moderated
    Nov 4, 2011 3:25 PM (in response to Kirby Krieger)

    Indeed - I should have added that I have several smart albums for themes I frequently work with...  but at this stage I think that might be a bridge too far.

  • CalxOddity Level 3 Level 3 (680 points)
    Currently Being Moderated
    Nov 4, 2011 3:35 PM (in response to CalxOddity)


         Once more unto the breach....


    I could maintain a set of highly elastic themes even under the most absurd construct.  Suppose every single image was stored on the hard Disk in a folder called Fred.  Also supposed each image in that folder was called Fred-1 through to Fred-65389.


    I import them into Aperture into Projects named "Freds 1-2000", "Freds 2001-4000", "Freds 4001-6000" and so on.


    I then assign keywords to each image from my *previously defined* keyword taxonomy.


    Thereafter, I have a range of almost infinitely variable themes to choose from through searching.


    Are you using keywords????

  • chacro Calculating status...
    Currently Being Moderated
    Nov 4, 2011 7:23 PM (in response to hotwheels 22)

    If you still have the original files in their theme folders you can easily keyword at import.... IF you are willing to ditch your current mess and start again you *could*:


    create a metadata import preset with keyword field

    import one themed folder and apply the theme keyword

    import the next folder with it's theme keyword into the same project

    and so on


    At the end of that you'd have all your photos in one project ( 'old stuff'), each with it's theme held in keyword.

    Then you make a smart album for each keyword and everything sorts itself.


    Seems to me you will have re-created your old themed folder scheme in Aperture, and with no manual sorting required. How much work this would be will depend on how many themes you have.


    Just an idea.

  • CalxOddity Level 3 Level 3 (680 points)
    Currently Being Moderated
    Nov 4, 2011 7:30 PM (in response to hotwheels 22)

    40GB of images to assign keywords to?  Pfft!  Been there, done that.  All completed. 


    The steps I took to migrate (this is not necessarily the *best* way, but this is how I did it):

    1. Got rid of unnecessary duplicates on the PC, because who wants to migrate something that isn't needed?
    2. Copied the complete folder structures from PC to Mac using the network
    3. I learned to use Aperture by importing 100 images and following tutorials online and manual and 3rd party book
    4. I created my library structure - Year Folder/Project (with the Project being and event, a shoot, a random set of photos, or a sequence taken from the window of a train over 2 months)
    5. I created an Aperture Folder called Work In Progress.  In this I created a Project called Imports Holding Pen - this is my default Project for imports and the imports always go to this Project
    6. I created my keyword taxonomy
    7. I then chose the first image folder and imported them into the Imports Holding Pen, leaving the images in their original location (I'm using referenced, not managed).
    8. I assign ratings, then immediately delete any 1 star images as they're a waste of time
    9. I assign keywords
    10. I then decide what the destination Project name should be, and create the Project with that name in the relevant Year folder.  You always have a datestamp of some description....  I sometimes split the images between 2 or more Projects - this can often happen if I've been away and have business photos and my own photos on the same card.
    11. Drag the images to their new home in whatever Project you chosen for them to live in.
    12. Go back to step 7 and repeat for the next folder etc etc


    ...and that's how you do it.

  • eltjofromu Level 1 Level 1 (85 points)
    Currently Being Moderated
    Nov 5, 2011 12:41 PM (in response to hotwheels 22)

    Hi Jon,


    What are the Themes and sub-themes you are talking about?

  • chacro Level 1 Level 1 (50 points)
    Currently Being Moderated
    Nov 5, 2011 6:59 PM (in response to hotwheels 22)

    hotwheels 22 wrote:


    Can I ask you if you see any important differences between organizing by theme outside of Aperture by folder before import and assiging keyword to the images upon import - as compared to getting the images into themed Projects from withing aperture and then assigning a keyword once you have them organized into Projects?


    I see. You are saying to do this as they come in and to put them all into one great big Project but am I correct in assuming you don't see any problem dividing them up into many Projects instead of one big one?

    I was assuming from some of your other posts the files were ALREADY existing in themed folders somewhere. I was suggesting a way that you could automatically assign keywords as they are imported, since it seemed like such a daunting task to keyword them individually. It's my inherent laziness that made me suggest that.


    I don't really see any difference in how you organize your library. I would encourage you however to start keywording and I just thought this would be an easy way to get it underway. Filtering your library by keyword or combinations of keywords and other metadata is an imensly powerful feature. It's probably the main reason I switched from PhotoShop and Adobe Camera Raw. I'm very happy to be free of the file tree.


    Actually, the advice from the other guy is good. You should just buckle down and do the legwork now so you can leverage the power of the program later. Use themed projects if you want to, but I wouldn't advise having multiple versions just for the sake of seeing them in different collections.


    Here's where I would ultimately want to end up if I were in your shoes. Put simply, I'd like to have a single master file for any given photo living in a project that made sense for it to be in so I could easily find it when needed. I would have versions of that master living in the same project so I could easily find the different ways I have processed the master in one place.


    I would keyword these in a way that was usefull for me. For you this might be your themes and sub-themes. I would then have smart albums to collect based on keyword or keywords: IE collections. I'd probably also have some dumb albums that I'd manually fill which I'd make on the fly as needed. And delete when done without fear that I'm losing anything but that temporary collection. Sometimes I use the light table for this..


    I would avoid duplicate versions as much as possible. There's no reason for it. It's simply what's known in all computing as version control. If you have duplicates multiplying all over the place for the sake of being able to see them in different collections, and later decide that this photo should really have a different white balance for EG, you have to hunt them all down and change all of them. If you only change one, then you're left not knowing for sure which one it was when you need it later.


    Likewise, as our skill progresses what was once a 5 star photo will in the future be a 1 star. If you have multiple versions you have to individually change all of them. If you have only one version in the library that shows up in multiple albums you only have to edit that one and all the others instances follow suit.


    There'd be nothing wrong with having themed folders and the same theme as a keyword if you'd like to keep your projects organized in this way. If a photo has multiple themes just add more keywords and it'll show up in multiple collections. Some of my photos have 5 or 6 keywords.


    You might consider importing your theme folders of files into similarly themed projects and applying a themed keyword thru the preset. But turn on 'don't import duplicates'. Then all you have to do is individually apply another theme keyword to have it show up in a different theme album as well.


    The real beauty of this kind of approach, rather than an old school file tree type thing, is that it's very easy to sort your photos by different criteria on the fly as needed. It's a fluid file system. Not locked down. Not easily mucked up.


    For what it's worth, I have projects by shoot in folders by theme. I have albums to see sub-themes across the entire library. It's a beautiful thing.




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.