Seating

BYCEPS’ seating model was designed to be flexible enough to fit both small parties (say, less than a hundred seats in a single hall) as well as big ones (like Northern LAN Convention – NorthCon – with around 3.500 seats).

Structure

Relations between entities

Each seat references these two entities:

• An seating area represents the physical location of a group of seats.

• A ticket category is meant to separate seats in different price ranges from each another.

  Since a ticket is bound to a ticket category, a user with a ticket from ticket category X cannot reserve a seat that belongs to ticket category Y.

Each seating area and ticket category belongs to a specific party since each seating setup often is party-specific (even if multiple parties are held in the same location).

Example: Small Party

A small party may take place in a single room or hall, and no distinction is made between the seats in it. Thus, a single seating area as well as a single ticket category are sufficient, so every seat belongs to the same seating area and the same ticket category.

Small party example

Example: Big Party

This is a setup for a party that is held in multiple halls and which offers seats in multiple price (and feature) ranges.

Big party example