Export images to a directory structure based on a collection tree?

A question:
Will lightroom have the capability to export images to a directory structure which mirrors a collections logical structure?
The reason I ask this is that when I create websites using third party tools (eg, Jalbum) I typically generate a flash or HTML based site with an menu structure for navigating the images.
So, the image interface is not simply a "flat-file" display as per the templates in Lightroom beta.
To do this, with previous image management tools (eg, iMatch) I create a hierarchy of images based on the categories (or collections) that the images are assigned to, export the images in a folder tree reflecting their categories (or collection), then use, say, Jalbum, to generate the website with the menu tree reflecting the folders/images.
This is extremely useful for more complicated image websites with categories and a large no of images.
If this function was built into Lightroom I guess it would be in the export function such that the "write to folder" box could take an argument {collection name} which would create a folder tree reflecting the collections logical tree which is being exported.
Apologies if this topic has been raised previously. But this function is extremely useful if you are using third party html tools or simply building websites by hand.
Regards
Alistair

I started simmilar thread in Lightroom Feature Requests few months ago, but can't find it anymore since new forum version...
What I can suggest as a new feature is export to directory structure from collections or second option from keywords. Probably more usable and easier to implement would be from collections.
What I need it to export many photos to different directories pretty often, and this would be great help since I could arrange them in collections and collection sets. Then select collection set and export it in a manner that collection set would be main export directory, and each collection within the set would be exported to its own folder within main collection set export folder.
This would be much appreciated feature in near future
Thank you for great product by the way

Similar Messages

Export Pics AND retain directory structure

I'd like to use Bridge to manage the photos I put onto my iPod, here's the general workflow:
All pictures are stored in directories by event (date) in the /pictures/ folder, for example:
/pictures/2008-07-01 Hike in Woods
/pictures/2008-07-02 Bike in Woods
/pictures/2008-07-05 Meeting with Tiger Woods
Here's what I'd like to do:
I rate all my pictures in Bridge using Color Labels (Green=Good, Yellow=Just OK, Red=Bad.
I'd like to use Bridge to select all "Good" pictures taken this year (easy to do using Search), but the rub is that I'd like to export these pictures but retain the directory structure. For example, I have a directory where I store all my pictures for my iPods and I'd like to retain the folder structure so that I can easily browse just my Good pictures on my iPod:
/iPodPictures/
/iPodPictures/2008-07-01 Hike in Woods
/iPodPictures/2008-07-02 Bike in Woods
/iPodPictures/2008-07-05 Meeting with Tiger Woods
This way, I can have iTunes monitor the /iPodPictires folder when I sync and copy over any pictures I move there, but only copy over the Good pictures and keep the rest off my iPod.
If I just do a Search, all the files show up in 1 window, and when I export, they are all put into 1 directory, which isn't easy to browse.
Any ideas how I can accomplish this using Bridge? I also own LightRoom, so if there are ways I could use that instead of Bridge, that would work as well.
Thanks!

I started simmilar thread in Lightroom Feature Requests few months ago, but can't find it anymore since new forum version...
What I can suggest as a new feature is export to directory structure from collections or second option from keywords. Probably more usable and easier to implement would be from collections.
What I need it to export many photos to different directories pretty often, and this would be great help since I could arrange them in collections and collection sets. Then select collection set and export it in a manner that collection set would be main export directory, and each collection within the set would be exported to its own folder within main collection set export folder.
This would be much appreciated feature in near future
Thank you for great product by the way

Workflow problems: Import selection, 9 keywords in list?, Exporting image attributes...

I have a few problems incorporating Lightroom into my work flow.
Is there a way to:
Select recursive directories when importing photos from disk without
a copy. Currently, I can only choose files directory(folder) by
directory.
Get more than 9 keywords in a shortcut list.
Add photos from a previously accessed CF card to a catalog in a short
time.
Currently it takes about the same time as loading a card from scratch.
Export image attributes to text file
(filename followed by keywords, rating...)
Basic principles of my work flow:
1. Flash card is used until contents roughly matches the archive media
size.
This means a 1GB card fills to 700MB after deleting rejects, and
a 4GB card will easily fit on a DVD.
2. Photos on card are categorized and rated/rejected/deleted one or more
more times while the card is being filled. This results in:
-Copies of retained images to the categorized directory structure on the
computer.
-Rejects deleted from card, and not appearing on the computer
-Category, and rating information for each image in an easily parsed
list.
3. Post processing is done and printing is done on highest rated images
in each category.
For example:
Day 1: start with a blank 4GB CF card, and shoot 1.5GB for customers A and
B.
Customer A has 8 subjects a,b,c,d,e,f,g,h; Customer B has 12
subjects
a,g,i,j,k,l,m,n,o,p,q,r. Note that some names for customers A and B
are the same. That night, I delete rejects off the card down to
800MB,
and copy the saved images to the directory structure corresponding
to each customer on the computer. Then a list is printed out to show
an image+rating list for each subject. Notes are made for each
"weak"
subject, so I know who to focus on in the next day of shooting.
Note I may have needed to do some minor post processing to determine
rejects and rating.
Day 2: I shoot 9 subjects for customer A: a,b,c,d,e,f,g,h,s, and 12
subjects for customer C: j,m,q,t,u,v,w,x,y,z,aa,bb. Similar culling,
sorting, and copying is done to Day 1.
Day N: CF card is full, so contents is written to a DVD, then card is
erased.
Day M: Sufficient counts of good images are obtained for Customer A, so
Final post processing is done, and prints are made.
My initial experimenting with Lightroom shows it has potential to streamline
the above work flow, but a few key hurdles have kept me from implementing
it. I have made some assumptions about the tool in the following description,
so the best help for me would first to point out what assumptions are incorrect
It looks like "import from device..." only allows a copy from the CF card.
A copy would mean once images were rejected in the catalog, it would be
out of sync. with the CF card. So "import photos from disk..." looks
to be the only way to accomplish principle 1 above. *[minor problem a]* I saw
no way to import the information from the CF cart recursively in this
mode. I had to choose the files in groups one directory (folder) at
a time. When I imported from device, I could grab the whole CF card,
even though it did a copy. Note another reason I can't copy the CF card
to the catalog is that the reject/delete operation would not free-up any
CF card space for the next shoot.
Rejecting, rating, and categorizing (with keywords) worked easily with
Lightroom, but *[minor problem b]* it appears the keyword shortcut list is
limited to 9 entries. Given customers can have more than 9 subjects,
it would be useful if this could be expanded, even if I implement some sort
of keyword hierarchy. I suspect the camera will complain about a bad file
format if I change any of the files on the CF card, but it looks like
the sidecar files on the computer disk allows me to "modify" images so
I can get a correct rating without actu

Do you mean by batches, or the occasional one-off look see? is this following useful? If so, I can tell you how to get it. <tiff:Orientation>1</tiff:Orientation> <tiff:YCbCrPositioning>1</tiff:YCbCrPositioning> <tiff:XResolution>1800000/10000</tiff:XResolution> <tiff:YResolution>1800000/10000</tiff:YResolution> <tiff:ResolutionUnit>2</tiff:ResolutionUnit> <tiff:Make>Canon</tiff:Make> <tiff:Model>Canon PowerShot S80</tiff:Model> <tiff:ImageWidth>3264</tiff:ImageWidth> <tiff:ImageLength>2448</tiff:ImageLength> </rdf:Description> <rdf:Description rdf:about="" xmlns:xap="http://ns.adobe.com/xap/1.0/"> <xap:ModifyDate>2008-01-04T15:31:04-08:00</xap:ModifyDate> <xap:CreateDate>2007-10-12T19:37:52-07:00</xap:CreateDate> <xap:MetadataDate>2008-01-04T15:31:04-08:00</xap:MetadataDate> <xap:CreatorTool>Adobe Photoshop CS3 Macintosh</xap:CreatorTool> </rdf:Description> <rdf:Description rdf:about="" xmlns:exif="http://ns.adobe.com/exif/1.0/"> <exif:ExifVersion>0220</exif:ExifVersion> <exif:FlashpixVersion>0100</exif:FlashpixVersion> <exif:ColorSpace>1</exif:ColorSpace> <exif:CompressedBitsPerPixel>5/1</exif:CompressedBitsPerPixel> <exif:PixelXDimension>3264</exif:PixelXDimension> <exif:PixelYDimension>2448</exif:PixelYDimension> <exif:DateTimeOriginal>2007-10-12T19:37:52-07:00</exif:DateTimeOriginal> <exif:DateTimeDigitized>2007-10-12T19:37:52-07:00</exif:DateTimeDigitized> <exif:ExposureTime>1/400</exif:ExposureTime> <exif:FNumber>8/1</exif:FNumber> <exif:ShutterSpeedValue>8643856/1000000</exif:ShutterSpeedValue> <exif:ApertureValue>6/1</exif:ApertureValue> <exif:ExposureBiasValue>0/3</exif:ExposureBiasValue> <exif:MaxApertureValue>116/32</exif:MaxApertureValue> <exif:MeteringMode>5</exif:MeteringMode> <exif:FocalLength>8564/1000</exif:FocalLength> <exif:FocalPlaneXResolution>3264000/286</exif:FocalPlaneXResolution> <exif:FocalPlaneYResolution>2448000/214</exif:FocalPlaneYResolution> <exif:FocalPlaneResolutionUnit>2</exif:FocalPlaneResolutionUnit> <exif:SensingMethod>2</exif:SensingMethod> <exif:FileSource>3</exif:FileSource> <exif:CustomRendered>0</exif:CustomRendered> <exif:ExposureMode>1</exif:ExposureMode> <exif:WhiteBalance>1</exif:WhiteBalance> <exif:DigitalZoomRatio>3264/3264</exif:DigitalZoomRatio> <exif:SceneCaptureType>0</exif:SceneCaptureType> <exif:Flash rdf:parseType="Resource"> <exif:Fired>False</exif:Fired> <exif:Return>0</exif:Return> <exif:Mode>2</exif:Mode>

How to create a tree based on directory structure

I want to create a hierarchical tree in Forms 6i based upon a file system directory structure (similar to Windows Explorer). How can I populate a tree with this information, is there something that I can call or write that would return the file system structure in a format that I can populate my tree?
Any advice would be greatly appreciated.
Thanks
Richard

Your link does not seem to work.They're re-jigging all the links to accomodate the hot poop on Oracle's latest and greatest, 10G. So at least the website is on schedule even if the actual software delivery dates have slipped :P
We can still get D2KWUTIL from here: http://te chnet.oracle.com/software/products/forms/content.html
Cheers, APC

I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders

I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders in Library view does not show images correctly: If there is a folder with sub-folder(s), the folder will indicate 0 images, but the sub-folders show the proper number of images. What happened and is there a fix? I tried uninstalling Lightroom and re-installing, but problem persists.
Here is a screen shot of the error message:
Message was edited by: Joseph Costanza, Jr.

See here for a solution.

Feature Request: Build Favourites Menu based on Directory Structure

Hi
SQL developer is really a very nice tool and even for DBAs. I would like to request a feature in this tool which would a good value to this tool and usability. Most of us have our own scripts which we keep on using to perform day to day activities, Can we have a feature which builds a menu based on the directory structure like one of the popular tools Benthic Software's "Golden" does? It would really be a very good feature to have.
I love sql developer tool already..
regards

Better support for file based development is being working on for our 1.1 release.
-kris

Directory structure of file based content server

Hi,
does anybody know how the contentserver manages his directory structure?
Looks like:
0ebf
0ec0
0ec1
0ec2
0ec3
0ec4
0ec5
0ec6
0ec7
I need to know the 4-digit directory in which my ID ( for example: 4bfee75d19d04548e10000000a320513) is saved.
Any ideas?
Best regards, martin

Hello Martin,
I've got the same Problem.
Did you solve it?
Massimo

Loading all images from Jar include the directory structure.

Hi I would like to puts all my images in a Jar. is it going to improve the loading speed?
I have a ImageLibary that load all the images to a hashtable and access each image by their path and filename.
I only have to input the image root directory and it will load all the images including sub-directory. If I decide to put these directories in a JAR. is this still going to work? Do all the class files has to be in the same JAR?
use getResourse()?
My current ImageLibary is like this:
public class ImagesLibary extends Component
private Hashtable imagesBank;
private Vector imagesName;
private MediaTracker tracker;
public ImagesLibary()
imagesBank = new Hashtable();
imagesName = new Vector();
tracker= new MediaTracker(this);
loadImageFile("./images");
for(int i=0; i<imagesName.size(); i++)
String key = (String)imagesName.get(i);
Image image = getToolkit().getImage(key);
tracker.addImage(image, 0);
try
tracker.waitForID(0);
catch (InterruptedException e)
System.err.println("Loading image: " + key + " fails. " + e);
imagesBank.put(key,image);
System.out.println("Loaded: " + key);
System.out.println("Total of " + imagesBank.size() + " images.");
private void loadImageFile(String dir)
File imageDir = new File(dir);
File temp[] = imageDir.listFiles();
for(int i=0; i<temp.length;i++)
if (temp.isDirectory())
loadImageFile(temp[i].getPath());
else
imagesName.add(temp[i].getPath());

is it going to improve the loading speed?depends :)
is this still going to work?some ajustments are needed... but thats done quickly.
Do all the class files has to be in the same JAR?no. but it's easier to handle.
use getResourse()?yes. don't know if u have to. but i do it this way :)
inside an application:
URL keyboardImagePath;
keyboardImagePath = (new Object()).getClass().getResource("/gfx/keyboard.gif");
Image kb=getToolkit().getImage(keyboardImagePath);inside an applet:
URL path = (new Object()).getClass().getResource( "/icons/right.gif" );
// now make the icon getting the gif from the url
ImageIcon = new ImageIcon( path );inside a hybrid:
URL keyboardImagePath;
keyboardImagePath = (new Object()).getClass().getResource("/gfx/keyboard.gif");
System.out.println("<-(application)load:"+keyboardImagePath); //if u wanna c what happens
if(keyboardImagePath==null)
keyboardImagePath=selfRef.getClass().getResource("/gfx/keyboard.gif");
System.out.println("<-(applet)load:"+keyboardImagePath); //if u wanna c what happens
Image kb=getToolkit().getImage(keyboardImagePath);hope that was helpfull :)

Export Masters To Organized File Structure

Hello Everyone,
I'm new to Aperture 3, in the past my photo library and folder structure has been a mish mosh of imports ranging from iPhoto to Picassa. The original photo structure of all my photos is a real mess. Of course, when I download Aperture 3, I jumped right in and imported all my photos (as referenced) then went about organizing them in Aperture.
I have looked around and not found the answer to this, but what I would like to do is take my Aperture Organized file structure and Export all the masters to a different location in the same organized File structure. Basically I want my "New" Master file structure to match my Aperture organized folder/project structure and store the referenced files on a share. Currently they are on my MBP with limited disk space.
I have played around with the export versions, but export Masters is grayed our when I select my entire "Projects and Albums". Any help would be much appreciated. I'm just trying to get better organized with my original Master jpeg folder structure.
Thank you,
Steve

scSaxon1 wrote:
Hello Everyone,
... what I would like to do is take my Aperture Organized file structure and Export all the masters to a different location _in the same organized File structure_ . Basically I want my "New" Master file structure to match my Aperture organized folder/project structure .... {Emphasis added}
(Added) First -- and this is important -- you must understand the difference between exporting an image (which creates a new file) and +relocating your Masters+ which moves your Masters to another drive location and tells Aperture where they are.
What you want to do -- quoted above -- can't be automatically (and thus usefully) done ... and (imho and apparently the Aperture design team's HO as well) there is no need.
Stepping into Aperture's world is bit like stepping off the solid pier onto a boat. You feel afloat. You worry about sinking. The boat won't sink.
Aperture is based on image-management. Until Aperture and like programs matured, photographers relied on +file managers+ and, basically, advanced file browsers.
Leave that behind. +There is no utility in having a one-to-one correspondence between your images and your digital negative files+. You literally can no not do this and use Aperture: Versions are images created on-the-fly, based on text files. They don't perdure as image format files (yes, I have been waiting a long time to use "perdure" in a sentence). Aperture lets the user manage their images (in tremendously plastic ways) and (except for backup) ignore file management completely.
I've touched on this in a few other responses in the forum. I'll try to find links. IME, the only file-management need I have is being able to find a file without Aperture. I keep all my Masters in their own directory (no one's captures but mine). I stick to a good file-naming convention. My computer sorts these tens of thousands of images by date in less than a second. I have never not been able to find a file almost immediately (as long as I know what I'm looking for).
If I don't know what I'm looking for -- I'll never find it using a file browser. That's what I use Aperture for.
I realize my presumption in assuming that your needs parallel mine. If they don't, specify exactly what functionality you are looking to maintain. Aperture may not be able to do it. My hunch, however, is that you are trying to stay moored to the world of file browsing. Push off -- there's good sailing out here.
Some additional thoughts and suggestions are [in this thread|http://discussions.apple.com/message.jspa?messageID=13294441#13294441]. And [here's a thread|http://discussions.apple.com/thread.jspa?messageID=13115722&#13115722] with even more.
Message was edited by: Kirby Krieger

Directory structure after upgrade to iPhoto 6

After upgrading to iPhoto 6, it appears that my photos were copied from the old, date-based structure into a new directory structure, but the old structure was left behind.
What is the layout of the new structure, and can the remaining old structure be discarded at this point?
Thanks for any insight you might be able to offer...

The new structure organizes photos into Originals and Modified folders. There is a third folder called Data that contains thumbnails created for the photos (smaller pictures used for better performance). These three are essential for iPhoto 6 to work.
Each folder contains a folder for each year (a year folder is created if you have even one photo from that year, e.g. a photo from 4/3/2004 will create a folder called "2004" and any other photos from that year will then be placed within it.
Every import creates a serially numbered Roll folder within the year folder. So if you import photos including IMG_234.jpg from 4/3/2004, for example, the location of IMG_234.jpg will be:
iPhoto Library/Originals/2004/Roll 1/IMG_234.jpg
And Roll 1 will have other photos imported in the same session. If you modify the photo within iPhoto (enhance, retouch, etc), the modified copy will exist in:
iPhoto Library/Modified/2004/Roll 1/IMG_234.jpg
The Data folder will contain a thumbnail for the image in the same path as the Originals:
iPhoto Library/Data/2004/Roll 1/IMG_234.jpg
So inside the iPhoto Library folder, you will see some files and those three folders with their sub-structure folders. Other things within the top level of the iPhoto Library folder, are leftovers from the previous structure - such as a folder called "2004" or "2005" that ISN'T inside Originals, Data, or Modified folders.
PhillyPhan's advice is sage. Don't mess with the insides of the iPhoto Library. However, I did verify on my own system after I upgraded, that year folders at the top level of the iPhoto Library are from previous versions of iPhoto. So you could move those, and those only, to a separate folder on your HD. I moved those off to a DVD-ROM and haven't seen problems since.
Remember: Don't touch any files, and don't touch anything within Data, Originals, and Modified folders.

Export Iphoto-library to file structure

I have been searching around for quite some while how to export the Iphoto-library into a 'classic' directory file structure (e.g. folder/event; folder/album,...).
Main raison for doing this is for backup and consolidation purposes: I have quite some 1000nds of pictures on traditional directory structures on my NAS; I want to consolidate this with the Iphoto data I have, without imoprting all the existing stuff into Iphoto.
I have found in fact 2 applications which should serve this purpose:
- the Iphoto to disk solution: http://www.iphototodisk.com, which seems no longer updated and the album export-feature was only in rel. 4 beta available
- Photoshare: a scripting based tool, but I experienced some issues witht the export of albums (empty...)
- a number of scripts found on teh internet.
I also read somewhere that a good alternativ eis to upgrade to Aperture, which seem sto have a better export-capability, including an export which allows to export to full library accoring to events and albums.
I'm surprise that there are not more apps availble for this,as it seems to be a hot topic on the internet.
Any advice ?
Peter

What advice were you looking for?

How to export images with Project Name to be visable by Photo Mechanic.

Hello all,
I am trying to create another complete set of my images, that can be edited by outside programs (Photo Mechanic and/or Lightroom). I am doing this by exporting the images out of a managed library. I want the Aperture "*Project name*" and Rating fields to be passed to Photo Mechanic. And then I want PM to be able to do queries on the Metadata fields containing the Aperture Project Name and Rating. My intention is to use Photo Mechanic to rename the images and relocate the images but still keep track of the Rating and Project Name.
In Aperture, when I add a custom metadata item under IPTC and export the image, that custom metadata item does not show up in PM or Bridge for that matter.
How can I export images and have the Rating and *Project Name* be exported and visible in PM or LR or Bridge?
Thanks in advance,
Dick B.

There is not an easy way but Ian Wood's tool might help you out.
Personally I would just use the "subfolder format" drop down options available in all of the export and relocate dialogs to sort them into directories that are based on Aperture project name - easy enough considering those other tools use file system based folders for there organization structure anyway.
RB

Using already existing directory structure to create rolls

I'm converting from iView into iPhoto. I have hundreds of directories titled things like 011606.SamuelWasBorn/ with subdirectories in there called /Images /FinishedImages /WebMedium /EmailSmall etc... and then plenty of .tif and .jpegs inside of those.
I've been doing this one Cmd-Shift-I at a time, followed by a Cmd-A t select all, then a Cmd-Shift-N for a new album, followed by retyping in the name and dropping the date.
Sigh. I'm 6 weeks into this now and still only 1/4 of the way through.
Has anyone tried to drag and drop an entire directory structure into iPhoto's directory structure, fire up iPhoto, and have it recognize all that stuff as a whole bunch of new rolls that lack thumbnails? Would that work? Would iPhot then offer to update its thumbnails? And then would I be happy and fully integrated into my new iPhoto life?
I'm just a bit too chicken to give it a try. If nobody's tried this before, I'll create a test library and give it a go, but if someone has experience with doing this, I'd appreciate any pointers.
Thanks.
Oren

Oren:
Welcome to the Apple Discussions. iPhoto creates a roll with the same name for any folder of image files that are imported into it. All you have to do is select your folders of source files and drag them into iPhoto's open window.
If you want to use iPhoto's alias feature you can keep your current source folders and drag them into a library that's setup to not copy the files into it but use alias files. The library works as a conventional library with the exception that if you delete a photo from the library it does not delete the source file. That must be done manually via the Finder. I've created some Tutorials to assist users to convert over to an alias based system or go to an iView based one.
I use iView as my primary image management and iPhoto's alias feature to create a library of the same source files. That way I have the best of both applications. Also, when using the alias method, the importing process is much faster. Good luck.

What should be directory structure for Custom MDS files?

Hi,
I have personalize a page and then exported the personalization.
Now my requirment is to migrate this personalization to other server, for which clients want steps specific to UNIX.
My doubt is where should I copy these files on the server to import the personalization using XMLImporter command? ( Client do not have JDev on his server, so can not use impot command)
my custom_top structure is like '/u02/int/applmgr/CUSTOM/xbol/11.5.0'
The customization is part of product 'OTA'
I am confused about where to put(Directory structure on custom top) customization and other MDS file to import using XMLImport.
This customization is also using a Custom LOV for which, I have given the path xbol/oracle/apps/ota/admin/enrollment/webui/XbolGradeRN.
For now I have transfered the file from window based JDeveloper and things are working fine. I need the UNIX directory structure for MDS files.
Please help to clear my this doubt.
Regards,
Adarsh

There is nothing specific to UNIX since the files are never picked from the file system on a production instance. You can place them under a temp directory with the proper package structure, the same way you exported personalizations for the seeded pages and the same custom package structure for your new pages and run import command. It's only how you run your import command matters, if you have placed the files in the proper package under some temp directory just give the -rootdir to point to your temp directory and no -rootPackage option.

Sub directory structure to Muse?

Please Adobe - when will you add a sub directory structure to Muse? The only workaround at the moment is to create separate discrete sites and ftp independently to the main site folder.

Oren:
Welcome to the Apple Discussions. iPhoto creates a roll with the same name for any folder of image files that are imported into it. All you have to do is select your folders of source files and drag them into iPhoto's open window.
If you want to use iPhoto's alias feature you can keep your current source folders and drag them into a library that's setup to not copy the files into it but use alias files. The library works as a conventional library with the exception that if you delete a photo from the library it does not delete the source file. That must be done manually via the Finder. I've created some Tutorials to assist users to convert over to an alias based system or go to an iView based one.
I use iView as my primary image management and iPhoto's alias feature to create a library of the same source files. That way I have the best of both applications. Also, when using the alias method, the importing process is much faster. Good luck.

Export images to a directory structure based on a collection tree?

Similar Messages

Maybe you are looking for