design-a-podcast-archive-workflow

# design-a-podcast-archive-workflow ## When to use - Use when preserving a show, moving hosts, consolidating seasons, or preparing a durable institutional archive. - Do not treat an RSS feed or streaming host as the only archive. ## Procedure 1. Define collection scope, owner, retention, access classes, repositories, and recovery objectives. 2. Assign stable IDs to shows, seasons, episodes, versions, segments, people, and source packages. 3. Preserve lossless masters, edit projects, published derivatives, artwork, captions, transcripts, chapters, and checksums. 4. Capture titles, descriptions, dates, contributors, languages, rights, consent, restrictions, corrections, and relationships. 5. Record feed snapshots, redirects, platform IDs, analytics cutoffs, and the source of every metadata value. 6. Validate decodability, duration, loudness, channel layout, transcript timing, links, rights, and package completeness. 7. Replicate across independent storage, test restore and search, and schedule fixity plus format-obsolescence reviews. ## Failure plan - Quarantine corrupt or ambiguous versions, preserve original bytes and metadata, and repair through a documented derivative. ## Worked example A network preserves eight years of episodes while moving hosts, retaining masters, feed history, corrected transcripts, music restrictions, and stable episode links. ## Done - A podcast archive plan records identity, assets, metadata, rights, accessibility, storage, validation, retrieval, and stewardship - Fixity, restore, search, playback, relationship, restriction, and feed-continuity evidence verifies the archive