Events

An "event" is a recurring opportunity that UTA agents actively work to slot clients into.

Event Series

An Event Series is used to represent recurring live performance events. Within Authoritative Data, an :EventSeries node is used to represent these events. Each :EventSeries, such as the Coachella Valley Music and Arts Festival (a.k.a. "Coachella") is linked to an :EventInstance node that represents a specific occurange (usually annually) of that event, such as the Coachella event in 2025. The series and the individual instances are modeled as such:

Party relationships

Although an :EventSeries is not a type of :Party, it can make use of relationships typically used by a :Party node such as relationships with :Name, :OnlineAddress, :Email and :ExternalRecord. Those relationships are connected to the :EventSeries, not the individual instances of the event as they do not change from one occurance of an event to another.

Event Instance

An Event Instance represents a single occurance of an :EventSeries. While many events are annual, others are held every other year or seasonally (i.e. Spring and Fall editions). The commonality is that each :EventInstance represents a cohesively organized edition of the event. For example, Coachella operates two festivals per year ("Weekend 1" and "Weekend 2"), but since they are organized, booked and operated together, these are modeled as a single :EventInstance held over multiple days.

Note that it is not uncommon for an :EventSeries to have multiple instances at different phases of booking at any given time. For example, the Glastonbury Festival may be announcing their 2025 lineup, booking final acts for 2026, and booking top-line acts for 2027, all at the same time. In this case, each year would be a separate :EventInstance.

Other considerations:

• For an :EventSeries that is held every other year, it is acceptable to model the event as an annual occurance with the :EventInstance for the off-year designated as a "fallow" event. See Event Tags below.

Linking to Locations

Location information is added to events through relationships with either a venue or location. In the diagram below, an :EventInstance is linked to a location (Indio, CA) with a LOCATED_IN relationship and a venue (Empire Polo Club) using a HAPPENS_AT relationship.

Note that some events are held in multiple venues as part of the same event. The example below shows San Francisco's Noise Pop festival, which is held in three distinct venues.

In the examples above, location and venue information is linked to the Event Instance. However, location and venue information can be connected to the root Event Series as well. This serves as a default location for the whole series.

Event Instance Day

An :EventInstance will have a specific date for which that event is scheduled to occur. In the example below, Coachella 2025 has 6 event days over the course of two weekends. Note that even though Coachella has two separately ticketed festival weekends in 2025, both weekends belong to the same :EventInstance.

Stage Instance

Stages are temporary structures set up within the context of a recurring event. Within the model, a specific :EventInstance can be extended to include descriptions of these stages using the :StageInstance node. These are useful elements to capture because they represent opportunities for our clients with each stage containing their own capacities, time slots, potentially different buyers, indoor/outdoor and other specifications.

The :StageInstance nodes used in the example below show 5 stages used within the Coachella 2018 event. Note that stages have an optional relationship to a :Venue but do not require an address. Stages are individually named, and may have their own connected :Configuration.

Event Series Hierarchy

An event series may also have related events held in other locations. In the example below, Lollapalooza events occur in Chicago, Brazil and Berlin. However, these events may only share the top-level branding of the "Lollapalooza" name in common and be produced and operated by completely different organizations. In this case, each of the regional event series become their own EventSeries and each is connected to a parent EventSeries using aj :IS_PARENT_OF relationship.

Operators and Buyers

An event series can also have relationships with other parties that designate whether that party operates of the event series or is a default buyer for that event series. Note that in many cases, an evert series operator is also the default buyer for the event. In the example below, that party organization called C3 Presents operates the Lollapalooza Chicago event series, for which they are also the default buyer.

For larger events, the party operating the event is often not the party responsible for booking talent. To allow flexibility for different buyer relationships, the :BUYS_FOR relationship can be used to designate different buyers for the :EventSeries, a specific :EventInstance of an event series or a specific :StageInstance within an :EventInstance. In the example below, C3 Presents is the default buyer for Lollapalooza Chicago, AEG Presents is the default buyer for Lollapalooza 2026, and Drumcode Records is the default buyer for the Perry's stage within Lollapalooza 2026.

Event Tags

Tags can be used to assign particular keywords to an Event Series. An :EventSeries can make use of two sets of tags: Type and Attribute. Event series types include event categories (such as "Festival", "Fair", "Concert Series", "Comedy Event", etc) while attributes include descriptions of the event experience (such as "Dry event", "family-friendly", etc). An :EventSeries can multiple tags of each type.

Event Attendees and Covering Agents

Parties of type Employee can be connected to event using two relationships: :IS_COVERED_BY and :ATTENDED_BY. The :IS_COVERED_BY relationship assigns one or more agents to an :EventSeries. These agents are primarily responsible for maintaining a relationship with the event's promoters and pitching UTA's clients for that event. The ATTENDED_BY relationship is used to maintain a historical record of UTA employees that physically attended a specific :EventInstance.