Use stable identifiers
Give the source session a stable key and identify each derivative separately. A cleaned audio export, a video clip, and a caption file can all depend on one recording. Record those relationships in a manifest. Filenames alone are fragile because editors often rename exports and distribution services may replace titles or normalize punctuation.
Keep transformation notes
Record significant edits, resampling, channel changes, and annotation revisions with enough detail to explain differences. A file hash can identify a particular binary, while a source key connects related versions. Both are useful; neither replaces the other. Retain a clear preferred version for each intended task rather than leaving buyers to choose among ambiguous duplicates.
Put the decision in the brief
For tracing podcast derivatives back to their source, make the expected treatment visible in the written project brief. Include one acceptable example and one case that needs a decision. Ask the source owner which supporting records exist and mark missing information explicitly. Review the assumptions before applying a rule to an entire archive.
Keep a reviewable handoff
Carry the agreed policy, source identifiers, and unresolved questions into the delivery manifest. A later recipient should be able to connect a finding about archive lineage to the exact file and version reviewed. Discuss project fit with Fiund before sending source recordings or sensitive contributor information.
Review checklist
- Define the project decision: archive lineage.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.