Podcast series and episode organisation

A podcast series relates published episode records to a show identity while feeds, release ordering and downloaded audio supply different parts of the catalogue.

A podcast series supplies the shared identity and description for published episodes. An episode record describes one programme; its media resource contains the sound or video. A feed distributes those records so a client can discover additions and updates.

For the fictional Harbour Notes, the chain is:

show: Harbour Notes
  -> episode: The First Crossing
     -> published media reference
        -> downloaded audio resource

The show's title and artwork describe the series. The episode's title and description describe its content. The download's file size and codec describe the stored resource.

Publication order and listening order

Programme pattern Useful starting order Additional context
Independent weekly conversations Newest release may be most relevant Topics remain independently understandable
A continuing documentary story Story sequence may begin at episode 1 Season and episode relationships matter
A feed mixing full episodes and trailers Role-aware selection A trailer is not another full story episode
Revised or reissued programmes Publisher identity and edition context A new date need not mean a new underlying story

A feed can list recent items first without prescribing that as the story's intended sequence. A serial production can require earlier episodes even when a newly published item is easy to discover.

A show can also expose different distributions: a public feed, an alternate-language edition or another programme selection. Sharing branding does not prove their episode records and audio are identical.

Downloaded and listened are separate states

A client may know an episode is published but not have downloaded it. It may have a local file that is still unplayed. It may retain listening progress while an old download has been removed.

These states answer different questions. Subscription discovery finds published records. Resource availability establishes whether playback can access the media. User history describes what this listener has done.

A locally stored episode brought into an Emby library has a resource and descriptive context. Recognising that audio does not, by itself, recover its original feed, subscription state or stable publisher episode identifier. Those relationships need to be retained by the workflow that supplies the resource.

Episode descriptions evolve

A publisher can correct a title or synopsis while keeping the episode identity. The identifier lets a client recognise the updated record rather than relying entirely on a display title.

The RSS feed carries the discovery and media-reference information. The actual codec and playable duration still come from the media resource; a show-level description cannot supply them.

See Also

References