Preset folders and destinations
Each participant preset carries its own folder pool — the set of destination folder names available in that preset — and every participant is assigned one or more folders from that pool. This is what decides where a photo lands when it is organized after analysis (that step itself is covered separately, see folder-organization).
On top of a preset's own folders, the app also has a second, independent mechanism: Export Destinations, a global list of export targets (each with its own base folder, subfolder/filename patterns, IPTC metadata, keywords and optional FTP/SFTP upload) that can copy analyzed photos out automatically at the end of a run, on top of whatever the preset organized locally.
How to use it
Per-participant custom folders (preset editor → Participants → row → Edit):
- 1In the participant's edit modal, use + Add folder under Custom Folders to attach one or more folder names — either…: pick an existing folder already used elsewhere in the preset, or type a new name.
- 2Optionally pin a folder to an absolute path with the 🔗 icon on its chip (Destination Path) — when set, photos go…: straight to that path instead of a subfolder under the normal output directory.
- 3"Also export to the default folder": (checked by default) — when on, photos of this participant go to the custom folders above and the standard {number} folder; unchecking it sends them only to the custom folders.
- 4Click Save Changes: New folder names are promoted into the preset's shared pool immediately, so they show up right away when assigning others.
Bulk assignment (Participants table → select rows → bulk action bar):
- 1Tick one or more participant rows; the bulk action bar appears:
- 2Assign folder…: opens a side panel listing the preset's folder pool — click a pill to append (or replace, depending on the panel's mode) that folder on every selected participant in one round-trip. The panel also has an inline + New folder form and a tri-state "Also export to default folder" checkbox (on / off / mixed across the selection).
- 3Clear folders: removes all folder assignments from the selected rows.
Editing a folder's name or path (Participants → folder chip → Edit Folder Name):
- 1Open the Edit Folder Name modal on an existing folder chip:
- 2Change Folder Name and/or Destination Path: If the folder is used by one or more participants, the app asks for confirmation before proceeding.
- 3Save: writes the change immediately to Supabase — the shared pool entry and every participant row that references the folder (folders[] and the legacy folder_1/2/3 slots) are rewritten in one transaction, on a serialized per-preset queue. A per-device path override in this browser's local storage is left untouched unless the edit actually changed the name or path.
Export Destinations (left nav → Export Destinations):
- 1+ New Destination: , then set a Destination Name, a Base Folder (Browse…), and a Subfolder Pattern / Filename Pattern using placeholders ({team}, {number}, {name}, {event}, {date}, {surname}, {seq} …).
- 2Fill in Credits & Contact and Templates (Headline, Event, Description, Person Shown) to control the metadata written…: to files exported here; Keywords to add fixed keywords on export.
- 3FTP/SFTP upload, under the FTP Upload tab, is labelled PRO in the UI; not gated in code:
- 4Toggle Default destination, or Auto-apply to matching images with a field:value condition, to control which runs use…: this destination automatically.
Limits and known behaviour
- The per-participant "also export to default folder" toggle and the Export Destinations feature are two independent systems: a destination's own subfolder/filename pattern does not read a participant's custom folder chips, and vice versa.
- Renaming a folder to a name that collides (case-insensitive) with another folder already in the preset or in a participant's own list is rejected — the app asks you to remove the duplicate first rather than silently merging the two.
- A per-device path override (stored in this machine's local storage) takes priority over the path saved on the preset in Supabase; it is how a shared preset can point to a different local folder on each computer.