Keep the recording lineage
A published episode may combine several sessions, introductions recorded later, and excerpts from an older conversation. Conversely, one recording session can become several episodes. Ask for both identifiers and a relationship table. Without that distinction, a collection can appear larger or more diverse than the underlying conversations actually are.
Preserve useful boundaries
Specify whether the project needs original session tracks, final episode masters, or both. A session can retain pauses and interruptions that an editor removes from the release. An episode offers the listening context audiences heard. Neither is a substitute for the other when the research question depends on turn taking or editorial structure.
Put the decision in the brief
For episodes are editorial units; sessions are recording units, 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 episodes versus sessions 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: episodes versus sessions.
- Identify the exact source files and recording edition.
- Document accepted treatment and unresolved exceptions.
- Agree on review evidence before preparing the full collection.