Add Ticket Schema

[lecafard]

Think we should create a table for individual tickets which can be linked to orders. Tickets will be generated when the order is marked as complete.

{
    id: uuid,
    showId: int,
    orderId: uuid,
    seat: string,
    // code for checking admissions
    code: string,
    used: boolean
}

[ad-t]

May I ask what the purpose of this would be (like an example use case)?

With the current approach made by @he-lium (found here), the order itself is the record of purchase and the entire order can be refunded if required. Additionally, we can combine the used and code fields in to @he-lium's approach so all of that required information is in one single record rather than scattered and containing duplicated information.

Additionally, the seats are no longer allocated, so we wouldn't require storing a seat identifier as well.

Let me know your thoughts @lecafard and @he-lium.

[lecafard]

Is there no reserved seating in the MVP?

[ad-t]

Is there no reserved seating in the MVP?

Correct. We figured it was conceptually simpler as reserved seating isn't completely necessary and without reserved seating you're allowed more flexibility and are not limited to a single location.

[he-lium]

We'd probably still need separate tickets, because group orders might line up individually (and should have separate tickets with different codes to show/print).

Regarding the used field, are we using rbs to track who's entered (like a barcode or something)?

[ad-t]

We'd probably still need separate tickets, because group orders might line up individually (and should have separate tickets with different codes to show/print).

I see. So would the entire purpose of the ticket records be keeping track of which tickets have been "exchanged for a seat in the show"?

Regarding the used field, are we using rbs to track who's entered (like a barcode or something)?

If we go with the above, that could be something that RBS could track.

[he-lium]

Yes, the tickets track an individual's entry to the show.

If we go with the above, that could be something that RBS could track.

This is probably a stretch goal, we'd need a new webpage and QR scanners to do that

[ad-t]

I agree with it being a stretch goal. It would be a fantastic feature to have, but I think we should prioritise getting the base system out as soon as we can.

I'll create an issue for it for when we get around to the next iteration.

[Qantas94Heavy]

Basic ticket table has been created, expanded scope can be tracked in future issue.