building an archive using collection names
Hi all,
I've been watching a recent webinar and saw David have a recipe that used the <session folder> token to define a sub-folder in the output location. He then selected all images in a smart folder (say, "3+") and processed them... and the images flowed nicely in sub-folders with the same names as the session folders they were in.
I want to (finally) make an archive of my pictures (jpgs) in my catalog.
My catalog uses referenced files, stored in a folder hierarchy (year/month). I have made several albums, using folders and groups to organise the pictures in a more human-readable and logical format. And yes, some images can end up in multiple albums. So I wanted the archive to have the same organisation as the catalog.
In a catalog, the <session folder> token doesn't work, but, there is a <collection name>. Great!
But… if you try the same approach as with the session, using a smart album to get the 3+ pictures, all files flow nicely in… the same folder named "3+". Damn.
OK, I can understand that. The smart album is a sort of collection. But that doesn't help me. The same for selecting "All images" and then filtering the 3+ pics outputs them in a single "All images" folder. Now what?
So, the only solution I see is traversing my entire catalog, collection by collection, filtering each one for 3+, selecting all pics in it and processing them. Not something I'm looking forward to. It's not even 100% what I need, because it will not recreate the collection hierarchy.
Note that I thought of using the <Image Folder Name> token so I could at least duplicate the folder structure of the catalog. Unfortunately, it only uses the last folder in the hierarchy, so I would get 12 folders, one per month.
Help!
Is there any brave and smart soul that knows how to do this? Preferably without having to reorganise my collection and/or folder hierarchy and naming.
Using C1 9.1.1, Mac OSX 10.11.4
Cheers,
Peter.
I've been watching a recent webinar and saw David have a recipe that used the <session folder> token to define a sub-folder in the output location. He then selected all images in a smart folder (say, "3+") and processed them... and the images flowed nicely in sub-folders with the same names as the session folders they were in.
I want to (finally) make an archive of my pictures (jpgs) in my catalog.
My catalog uses referenced files, stored in a folder hierarchy (year/month). I have made several albums, using folders and groups to organise the pictures in a more human-readable and logical format. And yes, some images can end up in multiple albums. So I wanted the archive to have the same organisation as the catalog.
In a catalog, the <session folder> token doesn't work, but, there is a <collection name>. Great!
But… if you try the same approach as with the session, using a smart album to get the 3+ pictures, all files flow nicely in… the same folder named "3+". Damn.
OK, I can understand that. The smart album is a sort of collection. But that doesn't help me. The same for selecting "All images" and then filtering the 3+ pics outputs them in a single "All images" folder. Now what?
So, the only solution I see is traversing my entire catalog, collection by collection, filtering each one for 3+, selecting all pics in it and processing them. Not something I'm looking forward to. It's not even 100% what I need, because it will not recreate the collection hierarchy.
Note that I thought of using the <Image Folder Name> token so I could at least duplicate the folder structure of the catalog. Unfortunately, it only uses the last folder in the hierarchy, so I would get 12 folders, one per month.
Help!
Is there any brave and smart soul that knows how to do this? Preferably without having to reorganise my collection and/or folder hierarchy and naming.
Using C1 9.1.1, Mac OSX 10.11.4
Cheers,
Peter.
0
投稿コメントは受け付けていません。
コメント
0件のコメント