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. ⚠️

Managing Groups of Photos in Library

Comments

4 comments

  • Walter Rowe
    Moderator
    Top Commenter

    Yes, look in User Collections. You can create albums, and you can organize albums into Groups or Projects. Projects can contain albums. Projects cannot contain other Projects. Groups can contain Projects and/or Albums. If you select a Project you can see all the images in all the albums within the Project. If you select a Group you will not see any images.

    It might be confusing and seem illogical that selecting a Group doesn't show you what's inside it but that's how it works. You can expand and close Groups and Projects in User Collections similar to "Folders" in the Folders tool.

    This article here on the support site goes into far more detail and has screen shot illustrations.

    https://support.captureone.com/hc/en-us/articles/360002516677-Virtual-organization-of-images-in-Albums-Smart-Albums-Projects-and-Groups

    0
  • Jon Coign

    Walter, 

    Thanks for the input. I do make use of the User Collections with a number of Groups and Smart Albums for adding a layer or organization that sits above the file system. I primarily drive this with Keywords. I read the article you linked as well as rewatched several of the YouTube videos on Projects, Groups and Albums to make sure I wasn't overlooking anything there, but I am pretty sure I am thinking of a different concept. 

    I am thinking of a way to group files in the folder view section of the catalog. Group here is obviously a bad term as it is overloaded with the groups in the User Collections. Looking around for other terms to better describe this I think this is a similar concept to what Adobe calls Stacks, where you can group a set of images and pick a default one to display. I think this would cover what I was discussing in item 2 and 3 in my initial message. If the grouping functionality used in culling tool could define these if chosen that would be very helpful. 

     

    The other item from bullet 1 in my initial message would be best as another layer to this where multiple physical files for the same image could be linked together. For the sake of discussion lets call this concept a "Set". The way I would envision this working is that rules could be set based on filenames that files with the same name before a special character like a dash (-) would automatically become a set. Certain metadata such as star ratings colors keywords could be tracked at the set level or at least propagated down to the other files. The idea probably needs a little more thought, but the situation I am seeing more often than not is I have multiple files created at different steps in the workflow that are all basically the same image, but as different external tools are used there becomes multiple files for each image. Lets take denoise for example. When this is one or two images it's not hard to manage, but when entire shoots are done at high ISO I often follow a process such as the following (simplified)

    1. Initial Culling of RAW files

    2. Batch Denoise remaining images

    3. Second culling of Denoised images

    4. Edit selects

    After step 2 I have two files for each image. It would be nice for these to be treated as a "set" and basically work with the newest image in the set. But then in the case you want to delete the set, both files are deleted. If you decide to only delete the denoised file, but keep the RAW any edits, ratings, etc you have made could be preserved without having to copy and paste from one file to the other. 

     

    Another way of saying this if when you "Edit With" or "Open With" in Capture One and either Capture One or the Plug In tool creates an additional file the catalog has no way of linking those files. I have situations where I use multiple plug-in tools that each generates an additional file. The Catalog should be able to link these files into a set know which file is the newest. 

     

    What do you think about those two ideas? Is any of that existing or is this more of a feature request?

     

    Thanks,

    Jon

     

    0
  • FirstName LastName

    Jon,
    I’m with you.
    I’m desperately keen for an enhanced round-trip to external editors (PS returning a fully compatible psd file in my use case). For me, it would be much simpler to return an edited file back to the C1 originating variant group or if no originating variant group to create one.
    Hoping The product team will consider
    Regards
    Richard
    p.s. yes, as you state, LrC stacks like functionality

    1
  • Jon Coign

    Richard, 

     

    I agree. Hopefully they will consider this. So far not much of a response to my post. I'll see if I can find a better way to submit it as  feature request in the next week or so. I've got to work on some repro steps for a bug I think I keep hitting in the keywords editor to log as well. 

    Thanks for replying. I'm sure the more people that mention this type of functionality the better chance of getting it added. 

     

    0

Please sign in to leave a comment.