Venue Authoring
Use this page when adding or editing a Venue. A Venue is a durable hosting identity with one current public location state, optional contact details and links, Event relationships, and an independently managed image collection.
What The Venue Form Owns
Section titled “What The Venue Form Owns”The shared Add/Edit form manages:
- Name, description, operational status, and optional capacity.
- One current location state: confirmed address, coordinate-only legacy data, or location TBA.
- Whether a complete exact coordinate pair may appear on public Wavemap maps.
- Public email, phone number, and a bounded set of external links.
- A compact Event relationship preview with a dedicated management sheet.
- Venue images when the current editor has the separate media permission.
The public Venue Index and Details maps consume this publication choice. An exactly published, coordinate-complete Venue can appear as a map point; a hidden, TBA, or coordinate-incomplete Venue keeps the surrounding public page usable and renders a neutral unavailable state instead of a fabricated location.
Location Review
Section titled “Location Review”For a confirmed address, search for a Venue, place, or postal address, select a candidate, and review the resolved provider-neutral snapshot before confirming it. Correct the snapshot manually when needed, or choose location TBA when the location is legitimately unknown. A suggested time zone is advice for Event scheduling; it does not silently change an Event organizer’s chosen reference time zone.
Editing loads the saved snapshot without calling the location provider just to display the form. Re-resolution replaces the current snapshot deliberately. Ordinary public pages show the formatted address but not provider provenance, raw provider payloads, or private address-transition evidence.
Resolved Venues default to Publish the exact location once the current address includes a confirmed latitude and longitude. Choose Hide the location from maps case by case for a secret, private, TBA, or otherwise unsuitable public location. TBA locations default to hidden, and the form and server both reject exact publication without a complete coordinate pair. Hiding a map point does not currently hide the formatted public address. Correcting or relocating an address preserves the saved choice until an editor changes it explicitly.
The public-location rollout changed every existing coordinate-complete Venue to exact publication. Existing TBA or coordinate-incomplete Venues remain hidden until their real location is resolved and reviewed; do not invent a point to make those rows appear on a map.
Events And Media
Section titled “Events And Media”The parent form shows only compact Event context. Use Manage Events for the full relationship set. When adding a new Venue, selected Events remain in the draft until creation. When editing an existing Venue, relationship changes save through their own revision-aware capability and refresh the compact preview.
Venue media is a separate collection even though it appears on the same page. The first profile-purpose image represents the Venue on compact public surfaces; the remaining ready images form its ordered gallery. If the Venue saves but an upload or final synchronization fails, use Retry Venue media. Retry resumes from the first unfinished image or repeats only the final collection synchronization; it does not create another Venue or reupload completed images.
Recovery And Trust
Section titled “Recovery And Trust”- A stale revision conflict keeps the mounted draft so the latest saved Venue can be loaded before another deliberate submission.
- Repeated create/update requests carry an internal request identity so a network retry cannot silently duplicate a successful parent write.
- Relationship and media capabilities have their own permissions. Scalar update authority does not imply either one.
- Mutation receipts and private address-transition records support data safety and later verification, but they are not the future human-readable audit trail for consequential admin actions.
- Map-publication changes retain actor, time, Venue, request, revision, and previous/next choice for later human-action verification. That durable record stores no coordinate history.