Lightroom: Export to sibling of current folder

  • 5
  • Idea
  • Updated 5 years ago
  • (Edited)
Currently, on export to Hard Drive, I use "same folder as original photo" then choose [x] Put in Subfolder and name the new folder. I'd like an additional option to say [x] Put in Subfolder of Parent and then choose the folder name. That way, I'm not stuffing exports further down the file tree but as a sibling to the current folder. Icing on the cake would be to be able to use the current folder name as a token in the new folder name.
Photo of sean

sean

  • 266 Posts
  • 44 Reply Likes

Posted 7 years ago

  • 5
Photo of Andreas Müller

Andreas Müller

  • 3 Posts
  • 0 Reply Likes
It would be nice if you could enter:

../jpeg

or even ..
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
This plugin supports export to sibling folder:

Exportant
Photo of Andreas Müller

Andreas Müller

  • 3 Posts
  • 0 Reply Likes
Exportant works great!!
I have 2012-12-12-Myevent/raw and Exportant exports to ..
so the jpegs end in 2012-12-12-Myevent

Now, if only Exportant could set the written file date to exif shooting date ...

8-)
Andreas
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Sean,

I don't see a way to do what you want using Exportant, short of exporting each branch separately I mean.

TreeSyncPublisher would do it, but you'd have to tweak the destination path for each project, (and the "source path"), since it doesn't support relative destinations, yet - thanks for the idea ;-).

I'm not presently aware of any "hands-off" solutions.

PS - regarding your " *** overwriting ... " hurdle, remedy by changing "Existing Files" in 'Export Location' section (next rev will have improved message).

R
Photo of sean

sean

  • 266 Posts
  • 44 Reply Likes
I'm puzzled why this isn't something that most people want. Right? Basically, I'm wanting to export out JPGs to a copy of the RAW file folder structure I created in Lightroom to manage my images.

All I need from LR is a way to use tokens such as "{current folder}", "{parent folder}, "custom text"... so I can select across all folders and export to:

PATH: {parent folder}/JPG/{current folder}
or even: ../JPG/{current folder}

done.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I think most people don't do what you do. Consider re-thinking your convention?

That said, I should have been clearer before:

You can customize Exportant to do what you want, but it would require editing bit of lua code in the "advanced settings" file (see preset manager section in plugin manager). Maybe one day this feature will be built in.

R
Photo of sean

sean

  • 266 Posts
  • 44 Reply Likes
My convention is to weed down 2000 shots per project into 5-10 folders depending upon project segment. Then, deliver a disc to client using these folders that classify the images. I know hundreds if not thousands of people that do this. (I hope they do this for their clients and not a huge dump of images in one folder!)
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I use TreeSyncPublisher to accomplish the same thing.

The difference being that exported photos don't come back to Lightroom - they are "set free" (so to speak)...

I can't say how many people do or should do what, but Lr has more than one fairly "glaring" omission ;-}. -handling folders for import/export and re-structuring folders is one of them, IMO.

PS - TreeSyncPublisher is one of my most popular plugins. - Jeffrey Friedl's FolderPublisher is similar, and for those collectioneers: CollectionPublisher.

I know of another person who keeps exported jpegs in a separate catalog, i.e. one catalog for masters to edit, another catalog for exports for viewing, slideshow, ... - different ways to work...

R
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
Published Folders are great. But I have this problem with it:

Because I do a lot of project work, I need to store images
in a specific folder structure. Several sizes and vrsions of the same image
are placed in one project folder.

Problem:
For every size/publish service (harddisk) I have to recreate the whole
folder structure because publish services seem to be device oriented.
Or I can export manually and choose a folder there.
This is VERY time consuming.

Please help me solve
this severe and workflow obstructing problem.
Maybe there is a way to spray publish sizes/options onto an image,
or can the folder structure be created automatically ... ?

This reply was created from a merged topic originally titled
Project/Folder oriented publishing in LR.
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
This is my workflow:

I see Lightroom as a DAM. This is my "image center".

When I start a project, in the early stage several selected but not edited images are published as previews in small size to the project folder from Lightroom.
These can be placed in a layout software.
A copy of these are published to an online service/ftp as web optimized, watermarked files for a client review with the same folder schema.

Further into the project, images are edited and republished for final use in the third party software, now in a higher resolution but same file format.

Some of the images will be ordered as a print for the customer, so they are published in a specific file format, to a different base folder - but using the same folder structure.

A set of images from this project is published to an ftp location in sometimes 5 varying sizes, using the folder structure - but placed in subfolders which are named according to the size.
When images are edited in Lightroom, they are republished and updated throughout all of the locations.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Originally written as comment to Foto VI.

I realized long ago that using Lightroom for original sources *and* exported copies was going to complicate things, so I only have the master copies in Lightroom, then export to various (parallel) trees which are not in Lightroom, for various consumption purposes. There is just no way I can think of to do what you or sean wants, as reasonable as it may seem (natively I mean - some other ideas involving plugins are listed below), and it does seem perfectly reasonable to me, although at this point I have adapted my workflow.

A lot of people export for immediate consumption only, then delete after using. But if you want all of them available for random access, read on...

I'm sure Adobe has heard your plea, but what do you do until Lr5/6/.../N?

A few ideas:
1. Customize Exportant to export the way you want (to project folder (e.g. same folder as original) in parallel mini sub-trees). *** SEE UPDATE AT BOTTOM.
2. Use CollectionAgent in conjunction with CollectionPublisher to clone project collection structure, then CollectionPublisher to publish those structured collections as folder trees to match.
3. Abandon project subtrees in favor of a set of parallel trees, like I do.
4. Export to common directory and use filename instead of subdir to distinguish.

I like #3 because I only do one thing with my photos at a time, and this approach eliminates the need to wade through unrelated subfolders. For example, if I want a high-rez copy, I visit the hi-rez tree, and in it, there are no subfolders for lo-rez copies to get in my way. I can see if your projects demanded thumbnails, and hi-rez, and lo-rez to have a common parent, this approach would not work (I have such projects too, but they all use dedicated custom publish services).

Another variation of #3: consolidate parallel trees into your preferred tree structure using a folder-sync utility such as Scooter Software's Beyond Compare.

Actually, what might be optimal for you and your like-minded cousins is a plugin which exports multiple related copies, in one swoop, e.g. one could define independent settings for each copy, including subfoldering, then quickly export all with a single service. - ok, *NOW* we're talkin'... Maybe first export a full-rez tif as temp file, with baseline processing (e.g. so it matches raw), then re-export that for the other needs. It's a lot quicker to export a tif as jpeg with only output sharpening or resizing..., than re-rendering the raws for each copy. I wonder if somebody has already written such a plugin.

Maybe somebody else has some other ideas for you.

UPDATE: I just realized that Exportant can do what you want out of box (no customization), since (unlike native subfolder field), you can use ('..' and) path separators in it.

So you can have, for example:

projects
project1
raws
jpegs
small
medium
large
...


and export raws to original folder (no subfolder) and setting sibling folder to
jpegs/small and jpegs/medium and jpegs/large (in separate export services).

Reminder: Exportant is not a "well-behaved" post-process action - meaning it's not compatible with publishing services like Flickr..., since it violates expectations by not putting exported photos in the expected spot. So you'd have to do such things in a separate phase (e.g. publishing those exported jpegs to flickr in original format using a separate publish service).

R
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
Hey Rob,
I am revisiting this thread and only now appreciate the wealth of plugins, you offer :)

How do I configure Exportant to output multiple formats in one go?
Is there a tutorial?
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
I wish there was an option, to define renditions based on a folder structure,
rather than a folder structure inside of renditions based on the publish sevice.

A simple solution:
a publish service, that allows to define
output parameters (size etc.) per folder inside of it.
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
A publish service that mirrors another master publish service would achieve the same goal, but I don't know if that is a viable option.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I'm getting confused (actually, I already was).

I'm not seeing any mirrored folders, I see:

loresbase / project
hiresbase / project
hiresbase / project / 1200x1800
hiresbase / project / xres

plus

base / customer / project / imgfolder / book section

all of which are to come from source files in this folder tree:

base / type of work / type of customer / customer / project / sessionnumber

Did I leave any out? or did you?

Ya say this is just a sample/example or is this it at least for now, and for a while...

Are there external constraints governing this stuff or are you just makin' it up as you go along, so to speak ;-} ;-).
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I gotta sign off for some hours zzzzzz.......
Photo of Foto VI

Foto VI

  • 77 Posts
  • 6 Reply Likes
sorry Rob, didn't mean to confuse
This is a real use case, not just some example.

Let's continue the conversation via email,
so I can be more explicit and make more sense of it.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
Your email helped to clarify - check your inbox ;-)
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
One of my problems - there is often multiple ways of solving the same problem. I've got so dang many plugins I can't remember what all they do ;-}.

Anyway, I think the easiest solution would be to use TreeSync Publisher - one of the most recent changes involves publishing back to source tree in a subfolder.

If you set up one publish service for each, then you just have to publish each and the job is done. Consider 'Publish Service Assistant' if you get tired of visiting all 5-6 publish collections each time...

Do you think that will work?