Page Comparison

...

• Each league/tournament/etc allocates sequences of game numbers to each schedule

• Game numbers are only unique within each schedule and may be reused in other schedules

• Game numbers often have a prefix and suffix to identify which league and category

• A schedule with groups/flights will have a sequences per group (flight 1 will have 1000-1999, flight 2 will have 2000-2999, etc within the same U13 schedule)

• Draft games can be have their numbers re-sorted based on the date/time prior to publishing, but published games cannot be re-sorted

  • Renumbering is a manual action. Automatically doing so may cause confusion as people use numbers as a reference while scheduling, so it’s usually only done in preparation for publishing

...

Currently we have a (published) games table and a drafts table, where drafts essentially act as isolated containers of a schedule.

...

• It will be possible for someone to create a published game, which would use U13L1000, then generate 100 draft games which would be numbered U13L1001 through U13L1100. Before publishing these draft games, someone could create a directly published game without using a draft, which would use U13L1101 as the next number in the sequence.

  • At this point there are only 2 published games, 1000 and 1101, while 1001-1100 are unpublished.

  • Likewise, if you were to create another draft game at this point, the next draft game number would be U13L1102.

  • When publishing games, this would most likely cause a shift in game numbers due to the already published games

• Deleting a game would create a gap in the sequence. Should this gap be automatically identified and reused or ignored?

  • You could publish games 12000 through 1299 and then delete 1250. If you generate 3 additional games, should the next games be numbered as:

    • option 1 : 1250, 1300, 1301, or

    • option 2 : 1300, 1301, 1302?