How to Organize Split Seasons and Midseason Breaks

A season-part crosswalk keeps one authoritative season and episode sequence while mapping release blocks and source-specific labels as reversible presentation layers.

In short: Keep the authoritative parent season and original episode sequence intact. Represent Part 1, Part 2, or a midseason block as a presentation group when it is not a separately defined season. Record each block's release window, official label, source-specific aliases, boundary episodes, relevant specials, and confidence. Then test that progress advances across the break without resetting or skipping.

A release pause changes how a season is delivered, but it does not automatically create a new season. Source menus may split or renumber the same episodes differently, so the library needs a crosswalk rather than another guessed hierarchy.

Build the season-part crosswalk

Keep aliases so users can search the label they encountered without making every alias a new season.

This crosswalk also keeps future corrections local: a changed source label can be remapped without renumbering episodes or rewriting completed viewing history.

Verify the parent season

EIDR's public hierarchy places seasons under series and episodes under seasons. Check whether authoritative metadata creates one season or multiple season records before adding local part groups.

If there is one season, preserve it. A source's “Volume 2” or “Part B” can be mapped as a release block. If authoritative evidence defines separate seasons, represent them separately rather than forcing one season for visual simplicity.

Preserve episode identifiers

Record original distribution number, title, and stable identifier where available. Do not restart episode numbering at 1 merely because a second block appeared later, unless the authoritative scheme actually does so.

Dublin Core hasPart and isPartOf relationships support the distinction between a season and its logical parts. A local display group can link to episodes without changing their parent identity.

Model the break explicitly

Store:

• last episode before the break;
• first episode after it;
• release dates or windows;
• whether a special appeared during the break;
• source labels and aliases;
• next-episode behavior;
• any spoiler-safe transition note.

Use the specials placement card when a special sits near the boundary. Do not absorb it into a part by default.

Test progress across the boundary

Mark the final episode of the first block complete in a controlled test. Verify that:

1. the next action resolves to the correct episode;
2. season progress does not reset;
3. the second block label is visible but not mistaken for a new series;
4. Back returns to the same season context;
5. source or version selection remains valid.

When resuming after months, the series recovery workflow should identify the break as a context boundary while preserving the last completed episode.

Handle conflicting source schemes

Create an alias map:

Do not choose a winner merely because one source is currently available. Preserve the authoritative hierarchy and map each source item into it with evidence.

Keep anthology structure separate

A split release does not determine whether episodes share continuity. Use the anthology workflow to model independent stories, recurring themes, or seasonal continuity without changing the release-block crosswalk.

Norva may organize series versions and compatible authorized sources, but season and part labels depend on connected metadata. Verify identifiers and sequence before correcting or merging source records.

Common mistakes and limitations

• Turning every release pause into a new season.
• Restarting episode numbers for a local part.
• Using current source labels as canonical history.
• Hiding specials inside the break.
• Failing to test next-episode behavior.
• Confusing release structure with narrative continuity.

Frequently asked questions

Is Part 2 always a new season?

No. Check authoritative season identity and episode parentage; a part can be a release or presentation block.

Should part labels appear to users?

Yes when they help navigate or match source terminology, but they should not replace canonical season and episode identity.

What if sources disagree on numbering?

Preserve source aliases and map each item to a verified canonical episode rather than renumbering the library repeatedly.