Export to folders corresponding to Session favourites
For many shoots my workflows is the following:
1. I select raw photos and sort them to folders in Explorer. I name folders like Party 1, Party 2, Party 19.00, etc. This way I always have photos sorted even if something happens to C1.
2. Then I create new session, and add folders with selected photos one by one to Session Favorites. This way I can easily switch between logically grouped photos or view All Images, if I need so.
Maybe someone would suggest better way, but I found using Session favorites to be a good way to be able to distinguish between sets and still no need to extra move files on hard drive.
3. When exporting I want to have the same structure - Party 1, Party 2, Party 19.00 - under Output folder. So far I can do it only by exporting photos from each Favorite separately, changing export settings accordingly. If I have 12 folders, this becomes tiresome.
My question - is there a way to automate export so that it would create folders according to Session Favorites under Output? I tried all variables for Sub folder that might be relevant, but none helped.
-
When you use Output Recipes there is an option to define the Output Location using naming tokens for subfolder(s).
On of the tokens is "Image Folder name".
If my understanding or your requirement is complete enough (so far) I think this should help to get you to the solution you need.
1 -
Thank you, SFA!
When checking tokens I was looking for such words as Session, Folder, Path, and missed Image Folder.
You are right, if I put "Image Folder name" token in Sub Folder field (this is important), then it works fine for my task.
Thanks again.
When you use Output Recipes there is an option to define the Output Location using naming tokens for subfolder(s).
On of the tokens is "Image Folder name".
If my understanding or your requirement is complete enough (so far) I think this should help to get you to the solution you need.
0 -
It's great that that worked for you Anton.
"Session" or "Catalog" names can also be included. The "Document Name" token does that job as I recall.
In effect that is a good token name choice even though it is not instantly intuitive!
There may be others of similar opaqueness to be discovered ...
0
Post is closed for comments.
Comments
3 comments