Rightroom: How to re-initiate a published folder?

  • 2
  • Question
  • Updated 5 years ago
  • (Edited)
So recently I have noticed that all my published folders have been emptied, this goes for flickr, all my clients and other published folders.

I know how this has happened, I have recently changed my ingest naming convention and thought I'd just as easily rename this year to keep it all up to date. I did this from within LR. Right click, rename.

When given an option to rename a file within LR, why does it not remap the published service content, instead published folders will emptied as there are no folders to link back to, hence the folder name change.

Makes sense, if you rename a path then you loose the link, but why not remap the path when renaming from within the GUI

Is there a way to re establish this connection, and if not, why not put the UID of the image as a link to the published content and not the containing folder. Especially as you have a rename option from within LR that does not remap.

Please change this to an idea if applicable
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes

Posted 5 years ago

  • 2
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Just as an amend, my actual finder folders are still in place with the relevant images and sidecar XMP files, all intact.

We need a 'snyc folder' under the hard drive publish prefs.
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
I dont want the sync button to affect anything already on Flickr, just to make local changes before publishing
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
folder path changes, name changes etc etc
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 372 Reply Likes
Stuart,

I agree: there is room for improvement when it comes to association of published photos with their source photos, e.g. to support renaming...

As it stands, it's left up to each publish service, and there is no "event broadcast" or anything like that to let those publish services know that photos have been renamed (unlike "deletion" for example, in which case there *is* such an "event" broadcasted).

Anyway, you may be able to hack a fix but there is no "ordained" way to do it that I know of - sorry: I think you gotta pretty-much republish everything after a rename..

EDIT: did you rename files, or just folders?

Rob
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Hey Rob.

Just folders, I changed my ingest naming convention and I wanted to replicate that folder change for everything this year. (Old stuff is archived and I'm fine with it being as it is) So, rather than having half of March one way and the other half another, I decided to go into lightroom and affect the change to reflect my new folder names. This was from within lightroom, Right click and rename. I didn't rename files just folders. Luckily for me, when i set up a publish folder for a client etc, i always keyword with that client or service, so anything goes to the wall, I can filter the images and set up a new service.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 372 Reply Likes
Hi again Stuart,

I'm getting confused.

I assume by "Published Folder" you mean "Published Collection".

If you repopulate published collections somehow (they became empty after the folder rename, right?) can you not mark all photos as "Already Published" and be back to where you were? Or are the photos with renamed folders being considered different publish entities now (I can easily imagine either case).

?

Rob
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Hi

Yeah Published collection, as in a published hard drive service. You don't have the option to 'mark as up to date' unless the collection have been modified. All my folders are back as I have just had to drag the filtered images back, still took a while.

All that was needed was a update folder location button in the published collection and it would have been done in a fraction of the time

Pattie, Any thoughts on this?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 371 Reply Likes
OK, so problem was confined to re-populating publish collections - no need to republish (or mark as up to date).

Consider using smart collections for publishing instead, to avoid this issue in the future (or maybe Pattie can provide some info...).

Rob
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Well similar, I tag images with a keyword that's the name of the client or service. That way I just filter and drag back into the the published folder.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 371 Reply Likes
Why not use smart (publish) collections? (so you never have to drag anything anywhere, even when there are changes like to the recent ingestion conventions...).
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Yeah I have thought about it, but that would create another folder in my published folder and I have a few watch actions looking at some of these folders in order to upload via FTP, and I don't always, although they appear in a client folder; want to upload the images
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Which beings me on to:

It would be a great advantage to, when setting up a published hard drive service, to be able to set up that initial folder as a smart collection.

Yes, I understand that you can add a smart folder, but that's not always desirable, especially as like myself each folder is either being picked up by another catalog or being used as a watch folder for another service
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 371 Reply Likes
I'm getting confused again by terminology I think.

Publish services use collections, exclusively, not folders, so there is never a conflict between published collections and watched folders...

Setting up a publish service with an initial smart collection is exactly the same as adding one after setup.

First thing I do when I create a new publish service is delete the regular collection and add a smart collection.

Or, am I not grokking the conundrum?

Rob
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Setting up a publish service with an initial smart collection is exactly the same as adding one after setup.

That's my point, you can't. You can only add a smart collection once a publish service via Hard drive has been applied
Photo of stuartpeckphoto

stuartpeckphoto

  • 226 Posts
  • 2 Reply Likes
Not sure we are on the right lines here. You can't delete the folder as it's explicitly tied to the publish service.

I've set up a test just to show you. See how the smart folder is within the main folder that is created.



Image that test is my watch folder, now I have created a smart collection but it resides in the container folder, so therefore I can't delete the main folder as it would delete my published service

What I tend to do is, say i have a client called test, I set up a catalog called test and add the published folder. I then publish original images, when i open that test catalog all i do is sync the folders and all my XMP comes through, meaning I have a catalog for each client

Sometime however I use the folder to publish to, I then use that as a watch folder for Automator for instance.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 370 Reply Likes
Got it. Hard Drive publish service works differently than the publish services I am most familiar with, in particular:

"published collections" are called "published folders" and are associated with export location.

Although I am surprised the sibling smart collection export shows up as a child subfolder, I can see that is what's happening - learn something every day... - thanks.

R
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 372 Reply Likes
Note: one solution to this problem is to use TreeSyncPublisher.

It has a flat-folder mode in case you don't want tree-structured export.

Publish collections are not tied to export folders...

Rob