Lightroom: Aibility to add image to Lightroom collection/keyword in export options

  • 4
  • Idea
  • Updated 6 years ago
  • (Edited)
I think it would be very handy to be able, in the Lightroom export dialog, to add the original image(s) to one or more collections, or add an additional keyword, upon export. That way if images are regularly exported with a particular preset, say to a client folder that is not itself added back to the library, those original images can be quickly found in their collection should they need to be re-exported. This would be more convenient and reliable that having to remember to add them manually to the collection before exporting them.
Photo of Tom Gardner

Tom Gardner

  • 2 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 4
Photo of john beardsworth

john beardsworth

  • 998 Posts
  • 219 Reply Likes
The real solution here is to make History searchable via smart collections.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
I think searchable history is a great idea, and may (or may not) be ideal to cover Tom's needs in this case.

(suggesting it's the only "real" solution seems a bit presumptuous...;-}

Would there be any advantage for this being a regular collection, instead of smart?, or being able to enable/disable in the export dialog box case-by-case/preset...?
Photo of Tom Gardner

Tom Gardner

  • 2 Posts
  • 0 Reply Likes
Searchable history via smart collections is a neat idea I hadn't thought of. It probably would do the job most times, but the collection parameters would need to be tweaked to allow manual addition (say of retrospective members of the collection and/or any image that did not have the necessary history step). So you could manually add a non-exported special keyword and add it to the smart collection search terms. This could be very powerful for lots more uses than my request.

[10 minutes later...] Actually, I've just looked at this and the history only records that it has been exported, not any detail of any named export preset, so it would not be any use for my suggested purpose without this.

I think that the option I proposed is simple, flexible, fully under one's control, and intuitive. I see it working a bit like the Flickr publish collection, especially JFreidl's more powerful version, which allows you to specify additional tags to export with the image as well as add it to specific Flickr sets and groups. Also you can get LR to filter on images that have or have not been exported to Flickr.

Using multiple hard drive Publish locations, could also be used, though not quite what I am after. I need something that I can count on doing the cataloguing automatically as part of the 2-click export-from-preset workflow. The option (in addition to adding to a normal collection and adding keywords) to use this to add it to the above specific HD-location-specific Publish Collection would be the icing on the cake, making it even easier to re-export anything that I subsequently updated.

Some of the things (collection or keyword) I want to allocate at export time include:
Used for Prints; Used for cards; exported for x stock library; favourites exported to 'screensaver' location; exported to a client folder; exported for competition etc. I'm sure many others would have their own uses for this.

Even just the option to add one or more keywords to the original file would do the job: these could be chosen to be unique and made non exportable, then a smart collection make to collect these images together. Still, it's more steps to set up and not as simple and intuitive for anyone not as organised or familiar with these processes. Very powerful for the expert user, but a bit more of a workaround without a direct 'add to collection 'x' ' option.

I am sure it would be so easy to implement- it only has to add one or more fields to the the XML file/database record, plus a small additional section to the export interface. It's not like adding a whole new image manipulation tool. I guess it could even be created as a plug-in, if anyone feels like doing it.
Photo of john beardsworth

john beardsworth

  • 998 Posts
  • 219 Reply Likes
Making history searchable - and that would also mean LR recording more usage information into it - would resolve this specific need and much more. And it would do so without stuffing the IPTC keywords with information that doesn't belong there.

But if you want to do exactly what you are requesting, I am sure that a plug-in could do it right away.
Photo of Michael Watson

Michael Watson

  • 3 Posts
  • 0 Reply Likes
I agree it would be useful to be able to do these functions at export time.

I want to keep track of whether I need to send my image to my copyright holder, which library have I sent it to (so I don't send it to several) and similar functions which I will decide at export time. I will usually forget to tag it or put it in a collection beforehand.

A smart collection is the way to track this and export time is the time to mark it (preferably automatically)

I am sure a plugin could do it but I am not a plugin writer.