Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Projects & Groups - What's the difference?

Comments

2 comments

  • Jim_DK
    Hi Andreas,

    Pretty much on the money here. Groups do not limit the search ability of Smart albums, where as Projects limit the search to only albums in that Project. So Smart albums in a group will alwasy go back to the "all images" data base to look for matching images.

    The power idea is that I can set up fairly complex hierarchies using groups. If the Smart albums are looking for certain key words and the next time I import images with those key words, then they are auto filtered into the correct Smart albums.
    0
  • andreasbentzen
    Thanks for the response, James. Since it's apparently not possible to view all photos in a Group by clicking the Group icon under User Collections in the Library tab, Groups seems IMHO nothing more than a way of, well, grouping other stuff together so that it takes up less space in the Library tab when collapsing.

    Similarly for Projects, being a long time (too long?) Aperture user I think the big power of the Aperture library is that images catalog wise actually reside in the Projects, thus albums are not necessary for images to be viewable in a Project. With the current C1 implementation, one is left with having to create another album with all images, in addition to the albums with image selections for Project to be a really usable feature. Seems to be a less than ideal implementation I think, but then again I might be too locked in to the Aperture way of things.

    Is there a particular reason why clicking on a group, project or even a folder does not show all images residing within the underlying levels? Am I missing a reason why the current C1 method of only showing what's immediately in the level is better?

    Cheers,
    Andreas
    0

Post is closed for comments.