Proposal for Enhancements to the Project #650

Activity

1. evroon commented on May 3, 2024

   

   evroon

   on May 3, 2024

   Owner

   More actions

   Thanks for sharing your thoughts!

   1. Add a 'Referee(group)' Entity

   This would be useful indeed, but not something I plan to work on, contributions would be appreciated though.

   • Match Calendar: Implement a feature to schedule matches on specific dates, in addition to setting times.

   • Add 'MatchID' Property to 'Match' Entity: This addition would enable listing all matches in a table and facilitate the export/import of tournament data in formats like XLS/CSV.

   These are more frontend issues, start times of matches are already saved in a timestamp format, it's just easier to forget about the date part. Matches already have a primary key ID, though we could also add a column for string-based human readable IDs.

   Enhanced Statistical Information for 'Match' Entity: Storing detailed match statistics such as yellow cards, red cards, and suspensions in a JSON format could be beneficial.

   That's quite a big feature and still a bit vague to me, I don't want Bracket to be tied to specific sports where you use red cards for exameple, so it would have to be more generic/abstract.

   Detailed Match Results: For sports like snooker, tennis, or table tennis, recording detailed scores (minor scores) could enhance the depth of match results.

   I'm not sure what that entails.

   Expanded Match Results: Introduce more nuanced results such as 'A seized by referee', 'B seized by referee', and 'A and B seized by referee', along with a 'ResultMemo' property for special notes.

   That might be too much of a feature-creep for now, and I'm not sure what problem it would solve.

   Tournament States: Define states such as [Draft], [Running], and [Archived] to manage the tournament lifecycle more effectively. In the [Draft] state, all data can be modified without entering match results. Once in the [Running] state, only match results should be updatable. Finally, the [Archived] state would freeze all data, allowing only queries.

   Interesting idea, I like the idea of archiving tournaments and making them read-only. In running state, more should be able to be updated IMO. Bracket should be flexible enough (and already is) to handle changes to team setups or changing team names etc. during tournaments, which is an important feature that other tools don't have.
2. Repository owner locked and limited conversation to collaborators on May 4, 2024
3. evroon

   converted this issue into a discussion #691 on May 4, 2024