Clean, Stable Addresses for Event Instances

A link to a single event instance used to be built on an identifier that came from your ticketing system, which is opaque to patrons and tied to one provider. Now each event instance has its own clean, readable address drawn from the same semantic scheme already used across your works, people, series, and seasons, so a shared link reads clearly and does not depend on which ticketing system you run. This brings the disambiguation you already have across your catalogue to individual event instances.

Clear addresses for every event instance

Each event instance now has its own address built from a short, permanent identifier that belongs to Basker rather than to your ticketing system, so it stays the same whether you use one ticketing provider or move between them. Two event instances on the same day, a matinee and an evening show, each get their own distinct address, so there is never any doubt which one a link points to.

Short links that keep working

Alongside the full address, each event instance has a short link that redirects straight to it. The date and event name in the address are there for readability, so if an event is renamed the link still resolves to the right event instance and quietly corrects itself. Links you share today keep pointing at the right show tomorrow.