Catalog file management

Rebel Hornet

• 31. Dezember 2014 20:16

Greetings.

I don't know if this is the right place to feature requests, please kindly point me to the right direction if not.

I'm new to C1 and I love it it is powerful!
I'm also a Mac/iOS software developer, Here are some item's I'd love to be improved over the next releases.

1: having to locate a file in the "all images" to be able to delete it is kind of counter productive.
I would like to have a choice when removing a file from a user collection. CO-8.x could ask If I want to remove from the collection or move to trash. I should also be able to set the default action in settings or as a checkmark on the delete dialog. send it to trash or just remove from collection.

2: Having to delete images one by one even if a batch is selected is also counter productive.
I would like to be able to select the files I want to delete and just trash them, from any location as stated in point 1.
Also one thing that other softwares(LR and Aperture) have a "marked for rejection" flag, this is quite useful to easily mark and trash files that have been marked for rejection on large imports.(delete rejected images menu command - with KB shortcut)

3: on import, when importing to catalog, I have to pre-create the user collection where I want my images to be classified. why not streamline the import process and make it a one step operation, I would like to be able to import the images to a user collection that is not already existant, why not allow the user to name that collection in the import dialog and create one on import instead of displaying the infamous warning icon.

That's it, I have nothing else but congratulations on the power, flexibility and stability of CO-8.x

Best regards.
Sandro.

0

• 

  H. Cremers

  • 1. Januar 2015 13:22

  Good suggestions, even if i don't use CO's catalog functions.
  
  The right place would be a feature request in the form of a support ticket (via the website), this is the way Phase One's dev team keep track of requested features (and bugs). They don't scan the forum for this.

  0
• 

  N Belll

  • 12. Februar 2015 12:33

  Hi Sandro
  
  You may have figured a couple of these things out for yourself by now, but in case it helps:
  
  1. You're right that when you add files to CO it puts everything into All Images, the master collection. Therefore, deleting it from a User Collection doesn't assume that you don't want to have it in another collection, smart album, or whatever.
  
  2. You have found a "gotcha" that I just mentioned somewhere else. Any actions on a selection of images only apply to the Primary variant, i.e. the one with the thick white border in the Browser view, *unless* you make sure that Edit All Selected Variants is checked under the Edit menu or via the toolbar icon. Then, all selected image variants will be deleted when you hit cmd-Del. I have this enabled by default and switch it off temporarily if necessary, because my assumption is that generally if I select a bunch of files, it's because I want to do something to all of them simultaneously!
  
  Now, regarding the "Rejection" flag, you can do exactly the same thing in CO. If you hit the minus key it will apply a Red tag to the image. In Aperture, Reject is a function of the Rating but here it is applying a tag. You can then mark all your deletions (and if you like you can set a Filter on your view to hide images tagged Red, to get the same effect as "Unrated or better" in Aperture), then go to your All Images, hit the button to filter for Red tagged images, Select All in the Browser view and hit cmd-Del. This workflow is pretty much identical to Aperture.
  
  3. This is something I have also found very frustrating in CO. I abandoned User Collections because they result in a lot of repetitive tasks for not much benefit (to me). I now use the Folders section in the Library, because my images are organised by project on disk anyway, though there is still a step involved in adding a file system folder to the CO catalogue. In case it's of interest, I wrote about my workflow in this thread:
  viewtopic.php?f=55&t=18153
  
  I'm still learning CO, but reading the things that other people raise on the forums and the replies is a great resource. In particular, the number of people switching from Aperture has resulted in quite a lot of help available for achieving similar results with new workflows.
  
  Nick

  0
• 

  Rebel Hornet

  • 28. Februar 2015 13:49

  Nick, thank you very much, amazing explanation!
  
  As you mentioned I did end up figuring things out, I've been working with it allot lately and at this point I'm almost ready to abandon the catalogue feature and migrate everything to sessions. Sessions seems to be a lot more evolved workflow wise than catalogue. Catalogue gives me more and more the impression of a half backed feature, it's incomplete, which has the result of slowing me down.
  
  all in all, the software is good.

  0

Post ist für Kommentare geschlossen.