Author Topic: Destination path variable  (Read 595 times)

Offline maxorenstein

  • Newcomer
  • *
  • Posts: 2
    • 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: 295
    • 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.