quba42 / go_tournament_organizer Goto Github PK

An interface is necessary, where the participants can submit their matches.
These informations should be submittable:

• black player
• white player
• result
• board size (dependend on torunament mode)
• optional: point difference

Requires at least the following fields:

• allowed_board_sizes a subset of 9x9, 13x13, 19x19
• time_model
• komi
• handicap (there are various handicap models, and it is dependent on board_size)

We need to find out in advance what to look out for, in order to create something in compliance with the GDPR/DSGVO.

Requires at least the following fields:

• tournament
• board_size (9x9,13x13,19x19)
• white_player
• black_player
• result

E.g.
Django (Python)
Vue.js (JavaScript)
Angular (JavaScript)

The project language is English.
However, our initial use case is a Go club in Germany, and the front end will need to be entirely German.

For saving the data of players and matches a suitable database is necessary.
The database needs to save

• players information (name, surname, age, date of birth, strenght, city, club)
• played matches (black player, white player, result, optional: handicap, optional: point difference) (dependend on tournament mode)
• tournament specifics (boardsize(s), komi, handicap rules, time rules, start of tournament, end of tournament, name of tournament, special rules)
• optional: history of changes. In the case that the tournament administrator had to change an already submitted game, the changes should be documented for future reference

Additionally the database needs to be compatible to the frontend of the administrator and participants, so that matches can get submitted, the administrator is able to manage all information from his interface, and (at some point) the current state of the tournament can be visualized

Requires at least the following fields:

• name (required) contains a string
• rule_set (required) contains a rule set (see #11)
• start_time contains a date time
• end_time contains a date time
• notes contains a string
• players contains a list of players (see #9)
• games contains a list of games (see #4)
• result

The responsible for the tournament needs an interface to control it.
This includes:

• managing the participants
• deleting/adding matches
• deciding start and end of the tournament
• managing tournament specifics (like boardsize, komi, time, etc.)
• extracting a result at the end of the tournament

• showing participants the current results

Requires at least the following fields:
name
surname
strength
city
club
dob or age