Choosing How to Build Complex Events

25Live provides multiple methods to build event relationships, each with its own set of features and benefits. 

You do not need to build a complex event if your event is simple enough to meet these conditions:

  • The event information (Name, Title, Description, Type, etc.) accurately represents the additional occurrence(s) being added
  • The occurrence(s) being added can have the same setup, pre-event, post-event, and/or takedown time (if applicable) to the existing event occurrences
  • All occurrences can be published to a calendar without fear of oversharing information or creating confusion.
  • There is a desire to keep all portions of the event under one reference number.

If your event is more complicated, you can use this information to choose the most appropriate type of event structure. There will be cases where using a combination of approaches might be the best way to meet very specific needs.

Guide to Complex Event Structures

Related Events

Related Event diagram of showing two levels of shapes: at the top are three circles side-by-side, representing events that are related. Each circle has its own occurrences connected to it on the bottom level.

Create this type of event if...

  • The event information (Name, Title, Description, Type, Description, Organization, Custom Attributes, Requirements, Contact Roles, Categories) of the existing event does not accurately represent the additional occurrence(s) being added
    • The occurrence being added needs a different setup, pre-event, post-event, and/or takedown time (if applicable) from the existing event occurrences
    • Either the existing event, or the newly created one, should not be published to a calendar without fear of oversharing information or creating confusion
    • Confirmation reports are needed for only a portion of the event
    • There is a need to break up invoicing of a series of events based on a date range or other business process related constraint
  • The ability to hide a portion of the event (using Object Security) is important
  • Read More:
Event Segments

Event Segments diagram showing three levels of connected objects: a top-level event circle, three event segment squares connected to the event from below, and a varying number of occurrence circles connected to the segments at the bottom.

Create this type of event if...

  • The event information (Name, Title, Description, Type, etc.) accurately represents the additional occurrence being added
  • Adding a name to the occurrence(s) will help to further define it (in addition to the event name)
  • The occurrence being added needs different setup, pre-event, post-event, and/or takedown times (if applicable) from the existing event occurrences
  • All occurrences can be published to a calendar without fear of oversharing information or creating confusion
  • There is a desire to keep all portions of the event under one reference number
  • There is no desire to invoice parts of the event separately
  • Note: When copying an event with segments, the copy is temporarily stored as a draft. Use caution if your institution disallows drafts.
Bound Events

Bound event diagram showing two levels. On the top level are side-by-side, connected circles that read

Create this type of event if...