Acoustics, Calibration & Asset Architecture
Practical Date-First File Naming and Folder Trees for Creative Assets
A folder full of final-v2 files leaves the next editor guessing which source and edit produced a delivery. Give each asset a date-first ID, protect the master, and put each export under its working revision. On a 240-file intake, you can verify zero duplicate destination paths and trace a delivered JPEG to its master in under two minutes.
Choose a date that stays with the asset
Use a zero-padded ISO-style calendar date, YYYY-MM-DD, followed by a project code and a sequence token. In 2026-04-09_lamp-study_s017, the prefix records the studio-local capture date, lamp-study identifies the job, and s017 identifies the seventeenth registered asset for that project and date. Sorting by name puts April 9 before April 10 and December before the following January. Keep the prefix on every descendant so a file copied out of its project folder still carries its identity.
Agree on one studio time zone and record it in the project log. A session that crosses midnight gets two date groups. The sequence can restart at s001 in the second group because the full asset ID includes the date. For artwork made entirely on a workstation, use the local date of the first saved source. For a legacy scan with an uncertain capture date, use the documented ingest date and mark it as such in the log. Keep this date through later revisions and releases. Record those events in the log with their own dates.
Give assets, revisions, and exports separate counters
Use the three digits in s017 for asset identity, r003 for a saved working revision, and e001 for the first rendition of a particular export specification from that revision. Use lowercase ASCII letters, digits, and hyphens inside project codes. Reserve underscores for token boundaries, and keep the extension that matches the file format. If a project routinely imports more than 999 objects on one date, choose four sequence digits before intake so every asset in that group sorts consistently.
For a two-camera session with 240 files, reserve s001 through s120 for card A and s121 through s240 for card B before both operators start. Log each card identifier and its original filename against the assigned ID. Two files named IMG_0042.DNG can then coexist with distinct IDs. Leave a gap when a file is rejected after assignment so old notes still point to the intended asset. Give one person control of reservations, or assign nonoverlapping blocks in advance for offline work.
| Stage | Filename | When to issue a new name |
|---|---|---|
| Master | 2026-04-09_lamp-study_s017_master.dng | Register a new source with its own sequence. |
| Working file | 2026-04-09_lamp-study_s017_r003.psd | Save a new revision at a meaningful edit or handoff. |
| Web export | 2026-04-09_lamp-study_s017_r003_web-1600x1200_e001.jpg | Advance the export number when settings change within the same specification. |
Copy, verify, and protect the masters
Build three sibling folders beside the project log: 01-masters/, 02-work/, and 03-exports/. Begin with an empty destination and map the source names before copying. Include card IDs in the source paths when filenames repeat. If raw files have sidecars, copy those with their raw partners and give each pair the same stem, such as 2026-04-09_lamp-study_s017_master with .dng and .xmp extensions. Count raw files and sidecars separately. For 240 raw files and 37 sidecars, expect 277 copied files. Compare each copy's SHA-256 digest with the digest of its mapped source and investigate any mismatch before releasing the cards.
Make the verified masters read-only for editing accounts, then restrict writes to the master folder itself on shared storage. A file can still be replaced or removed if someone has sufficient rights on its parent directory. Test protection with a disposable file under the same permissions using the actual editing account. Keep a separately recoverable copy and practice restoring a sample file against the intake digest. If an application writes sidecars or indexes alongside originals, point it at working copies or move its catalog into the work area before importing.
Keep the intake log where the next operator can find it. One row per copied file should record the card or source path, registered destination, and digest. If the intake is interrupted at file 173, check those logged destinations against the original source before resuming. Skip an existing file only after its registered source and digest both match. Keep a copy with a mismatched digest out of the master collection until the discrepancy is resolved.
Export from a specific working revision
Open the layered edit in 02-work/ and save a new revision before changing crop, retouching, or layers. If two editors need the same asset, designate one owner of the next revision or reserve revision numbers before parallel edits begin. Record which previous revision each editor started from. A larger number alone cannot tell a reviewer whether an edit includes another editor's changes. Record the accepted revision explicitly in the handoff log.
For a 4000 × 3000 pixel edit at r003, export a 1600 × 1200 pixel JPEG into 03-exports/web/r003/. Each side is 40 percent of its original length, so the aspect ratio stays 4:3. A print TIFF can go in 03-exports/print/r003/. Log the source filename, output path, color profile, and export settings so another operator can reproduce the deliverable. If JPEG quality changes from 85 to 75 with the same dimensions and color profile, increment e001 to e002. A different size gets its own dimension token and starts at e001. If the color profile changes while the filename fields stay the same, advance the export counter and log the profile. If an output path already exists, stop and check the log before writing.
When a delivery service requires a short name such as lamp-hero.jpg, make a separate handoff copy and log that alias against its full export path. Keep the studio filename in the project tree. Index the alias by delivery date or batch so a second delivery with the same short name remains traceable.
Migrate a live job in one small batch
Try the scheme on 12 files that cover the awkward cases: a duplicate camera basename, a raw and sidecar pair, an editable file with linked media, and a delivered export. Build an old-path to new-path map before copying anything. Check destination paths after folding case because two names that differ only in capitalization can collide on shared storage. Treat each proposed destination as occupied until you have checked both the map and the actual folder.
Copy the pilot batch into the new tree and relink a copy of the editable file. Compare byte digests before any intentional saves, then open the relinked file and render one sample. Look at the pixels around the crop edges and check the width, height, and embedded profile in the output itself. Leave the old tree available until active projects resolve their links and deliveries can be traced. If a link breaks after the move, use the path map to relink it and reopen the project from a second workstation before migrating the rest.
Verify the handoff before the next session
Have a colleague start with only the project folder and a delivered JPEG. Give them two minutes to locate the exact layered revision and the matching master. If they need a message from the photographer to identify the file, add the missing source relationship to the project log and repeat the timed handoff.
- Sort by name and confirm that April 9 comes before April 10 and
s009comes befores010. - Check that the destination has one entry per expected file and zero duplicate paths after folding case.
- Compare master digests with the intake log and confirm that the editing account cannot replace a test master.
- Open the accepted working revision and confirm that its linked media resolves from the project tree.
- Compare an export's size, color profile, and revision token with the handoff record. For the web example, confirm 1600 × 1200 pixels.
- Restore one master into a separate folder and compare its digest with the intake log.