Event Series

Event Series connect independently valid Events under a durable editorial identity. Use a Series when the relationship between occurrences matters to audiences—for example a tour, recurring club night, curated program, or annual festival.

Choose The Structure First

Every Series has one exclusive structure:

Structure	Use It For	Child Content
Direct Events	Tours, recurring nights, residencies, and other flat programs	Independently scheduled Events
Editions	Festivals, conferences, or conventions with distinct installments	Editions containing program Events

Category and structure answer different questions. A category such as festival, tour, conference, recurring-program, or other describes what the Series is. Structure describes whether it contains Events directly or contains Editions. Choose both deliberately.

A Series cannot mix direct Events and Editions. You may change structure only while it has no structure-dependent children, which avoids silently stranding existing relationships.

Series, Editions, And Events

Use each entity for one kind of truth:

Series: The durable identity, name, description, classification, continuity state, branding, general links, and optional Series-wide ticket portal.
Edition: One concrete installment with its own description, overall dates, broad location summary, official Venues, attendance scope, links, passes, and program.
Event: One independently valid occurrence with its own exact schedule, attendance contexts, Venues, Artists, links, tickets, and public page.

An Event remains valid and editable outside its Series membership. The same Event may belong to more than one Series or Edition when that reflects real programming. Removing a membership does not delete the Event.

Author Edition Dates Honestly

An Edition may begin in one of two complete states:

Dates to be announced: No program-window bounds are stored yet.
Scheduled: A complete date range or date-time range plus one reference time zone.

Do not enter placeholder dates to make an announced Edition appear complete. The public page can truthfully present program dates, attendance, official Venues, and program items as forthcoming.

The Edition window is an overall organizer-authored scope, not the detailed schedule. Each program Event keeps its own authoritative date, time, and time zone. Moving an Edition window does not reschedule its Events.

Official Locations And Attendance

Author official Edition Venues at the Edition level. This set can include announced festival sites before every program Event exists and should not be treated as an automatically calculated union of Event Venues. A broad location summary can describe a city, district, or region, but it is editorial text rather than map or filtering data.

The interface derives Edition attendance from current inputs:

Official Venues only: In person.
Virtual-attendance links only: Digital.
Both: Hybrid.
Neither: To be announced.

Information, registration, and ticket links do not make an Edition digitally attendable. Use the virtual-attendance purpose only for a real livestream or other attendance destination.

Build The Program

Direct Series membership is managed from the Series editor. Edition program Events and official Venues are managed from the Edition editor. Event forms display their current Series and Edition context and provide links back to the owning management form; they are not the primary relationship editor.

Program order currently follows each Event’s canonical schedule with a stable tie-breaker. Stage, track, featured, and manual ordering are not yet modeled. Concurrent festival items appear as a program collection rather than a misleading single-stage timeline.

Links, Tickets, And Media

Add ordinary Series links for durable identity-level destinations.
Add Edition links with the information, registration, or virtual-attendance purpose that matches their job.
Keep ticket destinations in the ticket section. They link to external providers; Wavemap does not own pricing, inventory, availability, or checkout.
Series and Editions each support one profile image and an ordered gallery.
When no images are present, public Details pages show one large placeholder and no empty thumbnail strip.

Media saves after the parent record because file storage has a different failure boundary. If parent creation succeeds and an upload or final media sync fails, retry the unfinished media work; do not create a duplicate Series or Edition.

Series and Edition forms preserve their JSON draft in the current browser tab while you navigate to a related Event or Edition form. A returning draft restores automatically only when it still matches the known saved revision. If another editor changed the record, review or discard the stored draft instead of silently overwriting newer work.

Browser-selected files cannot survive a page load through this JSON draft. The interface warns before navigation when unsaved media would be lost and requires a save or discard choice.

When a child form was opened from a parent editor, a successful save returns to that parent workflow. A standalone save offers a choice between the public Details page and a relevant editing destination.

Interpret Integrity Findings

The following conditions are valid but worth reviewing:

A program Event is partly or wholly outside the Edition window.
A program Event uses a Venue not declared as official.
An official Venue is unused by the current program.
A program Event’s attendance mode does not fit the Edition’s derived attendance scope.

These findings are warnings, not write blockers. They may reflect incomplete programming, an intentional satellite Event, or stale Edition scope. Correct the authoritative Series, Edition, Event, or Venue record after confirming the organizer’s intent. Nothing automatically rewrites child Events or parent Edition scope.

Lifecycle And Deletion

Series continuity is active, on hiatus, or ended. Edition disposition is confirmed, postponed, or cancelled. Those authored administrative states are different from derived temporal phase.

Series and Edition deletion is soft and relationship-preserving. It suppresses public traversal through the inactive ancestor without deleting Events, Venues, Editions, or relationship rows. Destructive content deletion remains a higher-trust capability.

Not Part Of The Current Feature

Automatic recurrence or generation of future Editions and Events.
Stages, tracks, featured ordering, or manual program rank.
Ticket prices, tiers, fees, sale windows, availability, or commerce.
Rich digital-Venue records.
Draft/public publishing, moderation, or approval queues.
Automatic integrity acknowledgement or repair.