[FRC BLOG] The Great Registration System Crash of 2016

[runneals]

Originally Posted by DaveL

If the issue had something to do with volume, FIRST could have a different day for district teams to register.
FIRST could even separate the districts further, by picking a different day for each district to register.

Originally Posted by Whatever

If there is I want: "A team set up automatic registration routine to make sure they got their first choice and that routine went nuts bringing down the server."

Both of these are very valid ideas that are both worth attempting (although I think I read the second one differently the first time). Why don't they do something like what they do in December with FIRST Choice, where it allows a team to put in events and rank them which they would want 1-5(10). This would allow teams to come up with a list of events that they would want to attend, allow mentors to input them in their free time before the specified date, and then the slotting program be ran at a specified time to slot teams into events based on their choices that they made. For quite a few people, registration is not during their lunch hour so it could be hard for them to do it at work. The "slotting program" could also account for starting at 0 and working it's way up so older teams get first pick, but it could also include some spatial algorithm to allow teams to attend their closest event.
Allowing district teams to register on their own day would offer a way for IT to ensure that their systems would work for regional registration.

Just some random ramblings after reading this