Define possible combinations, restrictions and types of tickets

[TomNaessens]

This issue will summarize all the possible ticket variations and which are unique to a person and which are not. E.g. a person is allowed to buy multiple tickets for food and drinks (drankbonnen) for an event. But for the same event, he is only allowed to buy one member-only card, linked to his UGent ID.

This is a very important issue and will be the starting point of the restriction implementations of the 2.0 version. We have to make sure that we work out a good strategy before implementing it because changes later will be hard and cumbersome to add.

Ticket types

At the moment, the following options are available for a ticker:

• Public: public tickets are visible to everyone, private tickets have no use at the moment and default to not being visible
• Member only: can only be seen and bought by members. A person can only buy one ticket of this kind per event.
• Hidden tickets: can not be bought by anybody, they can only be assigned through partners

The disctinction between public/private and hidden/visible is not clear and should be worked out better. The options should be combinable and this combined behaviour should be described.

Restrictions

At the moment, tickets have to contain a unique per event, but this will have to change to support multiple tickets like drankbonnen. This limitation actually does not make much sense as free and open tickets may be bought as frequently by anyone.

The addition of orders (an order consist of multiple tickets, tickets can only be ordered in an order and tickets only can be paid for by paying for the order) possibly makes this even more complex.

Goal

The goal is to end up with a defined list which covers all usecases and were all behaviour is clearly defined.