Instruction 05-anime-absolute-numbering-and-multi-episode: Reading

Anime libraries are difficult when three identities are treated as if they were interchangeable: the title printed by a release group, the episode number embedded in a source filename, and the episode identity exposed by a metadata provider. Absolute episode 027 does not inherently mean S02E03. That conversion is only valid if an authoritative episode-order table says so. Specials, recaps, unaired episodes, split cours, licensing seasons, and provider revisions can all shift the relationship. Select a metadata provider and episode order first, record that decision, and then build an explicit mapping from each source identifier to the provider's season and episode pair. Leading zeroes improve sorting but do not establish identity.

For a season-oriented library, a single episode is commonly named with a token such as S01E03. A file containing two complete, adjacent episodes can be represented as S01E01-E02. The exact syntax supported by a scanner must be checked in that scanner's current documentation; superficially similar forms are not guaranteed to parse identically. Do not label an ordinary long episode as two episodes merely because its runtime is unusual. Conversely, do not assign two independent media files to the same multi-episode identity. A range should normally be contiguous, belong to one provider season, and reflect content actually present in the container.

Multi-episode files have operational limitations. A media server may create two episode records that both point to the same file. Depending on the server and client, both records can show the full file duration, share a resume position, or begin playback at the start rather than at an internal episode boundary. Naming communicates identity; it does not create chapter boundaries or split the container. If independent progress and episode-level playback are required, retain separate source files or split the container only with a deliberate media-processing workflow that preserves streams and timestamps.

Specials require explicit decisions. A prologue may be absolute episode 000, a provider special, or regular episode 1 under different orders. Many season-based layouts use S00E01, but that convention must match the selected provider. Avoid forcing a special into the regular absolute sequence merely to make arithmetic convenient. Likewise, do not merge two ranges across a season boundary. A source labeled 012-013 could map to S01E12 and S02E01; that should be represented by separate files or handled according to documented scanner behavior, not guessed as S01E12-E13.

A safe workflow is identify, map, preview, stage, verify, and only then import. Preserve original source names until the proposed mapping has been reviewed. Use a manifest that records the source name, absolute identity, target season identity, selected order, and reason for any exception. Preview the media manager's parser before enabling automatic rename. Test a small sample in an isolated library, inspect episode matches and specials, and keep the manifest with operational records. Never use filename arithmetic as a substitute for metadata verification.