Retain meaningful changes
An edit record can show removed sections, reordered answers, inserted narration, or processing applied during production. Not every archive retains a full editing project. Ask for what exists, then document major transformations that can be established. A polished master should not be described as an uninterrupted natural conversation when its structure was materially reconstructed.
Connect annotation versions
Transcripts created before editing may need more than a global timestamp shift. Match annotations to the precise master they describe, and keep the earlier edition distinct. Where an edit map exists, use it to trace surviving segments back to the source. This supports reproducible selection and avoids confusing production choices with properties of spontaneous speech.
Put the decision in the brief
For why edit decision records matter for podcast datasets, 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 edit decision records 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: edit decision records.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.