Event Scheduling
Wavemap treats an event schedule as the organizer’s local calendar intent. An editor chooses the date, optional time, optional end, and the IANA time zone that explains those values. Wavemap then resolves the exact moments on the server.
The current Wavemap event editor is intentionally a plain foundation workbench. It proves difficult schedule and relationship behavior, but it is not the final visual, validation, accessibility, or information-architecture design.
Scheduling Vocabulary
Section titled “Scheduling Vocabulary”| Term | Admin Meaning |
|---|---|
| Reference time zone | The organizer context in which the entered dates and times should be read. |
| Date-only boundary | A calendar date with no claimed clock time or exact instant. |
| Timed boundary | A local date and wall time resolved in the reference zone. |
| Optional end | The event does not claim an end unless one is actually known. |
| Repeated time | A daylight-saving transition produced two possible exact moments; the editor must choose earlier or later. |
| Nonexistent time | A daylight-saving transition skipped the entered wall time; the schedule must be corrected. |
| Administrative state | An editorial fact such as scheduled, cancelled, postponed, or rescheduled. |
| Temporal phase | A current read projection such as upcoming, ongoing, or historical. |
Do not enter midnight merely to satisfy a date-only event, and do not invent a duration for an event whose end is unknown. Start and end may have different precision when that reflects the source information.
Venue Suggestions
Section titled “Venue Suggestions”A selected venue may provide a time-zone suggestion. The editor can encounter four states:
- No venue has been selected.
- One or more selected venues have unresolved zones.
- Every resolved venue agrees on one zone.
- Selected venues suggest conflicting zones.
The suggestion never silently changes the event. The editor remains responsible for confirming the event’s reference zone, including for digital events, hybrid events, and multi-venue events. Correcting or relocating a venue later does not rewrite an existing event schedule.
Event And Relationship Editing
Section titled “Event And Relationship Editing”Event creation may save a small initial venue set atomically with the event. Later venue changes use a dedicated save so ordinary title, description, state, or schedule edits do not accidentally replace relationships.
Artist–event relationships follow the same trust rules with a collection shape suited to a larger dataset. Quick native Wavemap surfaces can handle one-off work, while a future Payload CMS integration may support heavier curation, bulk changes, content management, and repair review. Both must use the same server-owned authorization, transaction, revision, and public-identity capabilities.
If another editor changes an event first, Wavemap returns a revision conflict instead of overwriting the newer version. Refresh the event, review the latest values, and deliberately apply the intended edit again.
Public Index Presentation
Section titled “Public Index Presentation”The Events Index presents the organizer-reference date and wall time as its compact schedule. Date-only Events remain date-only, and Events without a known end do not receive an inferred duration. Cancellation is an administrative fact shown separately from whether an Event is upcoming, current, historical, or indeterminate.
Table, gallery, and feed are different presentations of the same applied browsing state. An Artist’s View All Events action opens an Artist-scoped Events Index, and that relationship context remains in the URL while switching views or reloading. Selecting an Event uses its canonical readable slug plus immutable public ID.
Integrity Review
Section titled “Integrity Review”Time-zone rules can evolve, imported evidence can be wrong, and an invalid row can be introduced outside the ordinary authoring path. Operators can run a read-only integrity report that identifies matching schedules, projection drift, unresolvable values, or structural inconsistencies.
A deterministic repair candidate is a proposal, not an automatic correction. Ambiguous repeated times and invalid values require an editor or operator to choose the intended meaning. Approved repairs travel through the ordinary event update workflow and preserve revision and provenance history.
Not Yet A Finished Authoring Guide
Section titled “Not Yet A Finished Authoring Guide”The following remain future product work:
- Final field grouping, responsive layout, component composition, and interaction design.
- Complete client-side validation and accessible error presentation.
- A polished time-zone search and daylight-saving explanation flow.
- Venue provider search, address confirmation, relocation, and historical-location policy.
- Full event artist, series, media, ticketing, and digital-content workflows.
- Payload CMS editorial and bulk-management surfaces.
- Expanded Event Details viewer-zone presentation, attendance hierarchy, and public-page completion.