Author Topic: Destination path variable  (Read 1746 times)

Offline maxorenstein

  • Newcomer
  • *
  • Posts: 3
    • View Profile
Destination path variable
« on: September 10, 2025, 06:33:16 AM »
For major conferences/events, I have a complicated workflow that involves pre-building folder structures for each session of the conference, using hot codes for photographers as well as hot codes for all the metadata fields for each session.

I use a portion of the known folder path to call the metadata (for example, {pfpt:0,47}) to grab enough of a unique key for looking up the rest of the metadata.

Our workflow is:

- Ingest to a master ingest folder by date sorted into photographer folders
- Find the images for each session and move or copy them using PM into the session folder (into a subfolder for each photographer)
- After the photos are in that folder, apply the metadata template that pulls all the fields for that session and writes them

Essentially, were there a destination path variable activated upon copy/move, it would be awesome to be able to save a step and call that variable during copy/move and have the metadata applied during that step!

 

Offline Max Lemesh

  • Sr. Member
  • ****
  • Posts: 297
    • View Profile
Re: Destination path variable
« Reply #1 on: September 10, 2025, 05:30:12 PM »
Very interesting workflow and request.

Could you give an example of how it looks at each stage? I'm very eager to understand how it works and how this new variable could solve the problem, and also to see if I could adopt any of your ideas for my future workflows.

Offline maxorenstein

  • Newcomer
  • *
  • Posts: 3
    • View Profile
Re: Destination path variable
« Reply #2 on: Yesterday at 07:34:39 AM »
Would be happy to share after I wrap up an event I'm working on implementing this for!

Offline Jeff Vogan

  • Member
  • **
  • Posts: 53
    • View Profile
Re: Destination path variable
« Reply #3 on: Yesterday at 07:13:32 PM »
maxorenstein, this workflow sounds pretty similar to a workflow that I built out for a client. It sounds pretty similar. I believe that if the photographers utilize the {foldernum} variable by shooting, for example, the keynote speech in folder 100, Breakout panel ABC in folder 101, Speaker Bob Smith in folder 102, etc., you should be able to apply all of the necessary metadata, including identifying the photographer, using Hot Codes. That would save you steps 2 & 3 of your current workflow.

I believe that what you are trying to accomplish could be done using existing variables, and no manual folder creation would be necessary.

Offline Max Lemesh

  • Sr. Member
  • ****
  • Posts: 297
    • View Profile
Re: Destination path variable
« Reply #4 on: Today at 03:28:58 AM »
That's what I do as well, Jeff.
Did it for multiple rooms on a conference and then time coded the speakers in each room
But if that new variable could optimize current or spawn new workflows it would be great