Electronic registration and start time check for the first start corridor

[VoiToi]

In the first start corridor, classically we have to search for each competitor and tick-off his name if he's there at the right time.

This should be quite easily done automatically with the SI card reader and a lightweight application or a QuickEvent module.

Requirements for the standalone application only:

• import the start list, including runner IDs
• store the start list, including runner IDs
• store list of checked runners, including at least runner IDs, SI card numbers and check times.
• export list of checked runners, including all above

Requirements for the QuickEvent module:

• either super-stable internet connection and use the remote database in the finish / event center,
• or an offline mode, where QE would be acting basically the same way as the standalone application:
  • must be able to check incoming runners while the main database is offline
  • import the start list from the remote database to a local copy
  • store and export list of checked runners

Requirements for both standalone application and QuickEvent module:

• read SI cards
• when SI card is read, beep and flash the window:
  • nice sound + green flashing: the runner is registered and came within his minute or later
  • warning sound + red flashing: the runner is registered, but came early
  • awful sound + grey flashing: the runner is not registered with this SI card

Optional, nice to have:

• handle late starts (be able to confirm the late start OR approve and save a new start time)
• handle wrong SI numbers (assign a new number to runner ID)
• automatic list of checked numbers export or additive synchronization over internet (should be very fail-safe, expect bad signal scenarios)
• automatic start list import or additive synchronization over internet
• handle unregistered? Questionable, regarding to start fees and additional stress for start crew

[fvacek]

I started to play around and I've developed StarterTool for QE https://github.com/Quick-Event/startertool . Unfortunatelly, the project itself is in beta version and I have not resources to make it work on Android without any issues and also to put it to google play. There is rather complicated process to make it, not as hard but ... .

So my favorite way is to use CheckList for now, at least until I'll find some free time to finish the StarterTool. CheckList is not open-source, I've contacted O-checklist developer ( [email protected] ) and I'm still waiting for response.

StarterTool has many advantages, like:

1. automatic synchronization of start list, starters will see late entries, start times changes, SI updates, etc.
2. Starters can update wrong or missing SI on start, so competitor will be correctly couplet with it's run during card readout.
3. Acoustic signal are there and user customizable

Big disadvantage is the necessity of reliable mobile data connectivity, there are still many interesting localities without good mobile signal coverage. This is almost no-go for me.

O-checklist covers all the Requirements for the standalone application only IMO, so my advice is to add support for O-checklist to QE first.