search

ctnadovich / randowizard

Randonneuring.org web application
GNU Affero General Public License v3.0
0 stars 1 forks source link

Volunteer assisted checkin #10

Open ctnadovich opened 9 months ago

ctnadovich commented 9 months ago

It would be useful if there was something to give to a control volunteer that would allow that volunteer to quickly and easily check-in a rider they saw.

This seems relatively straightforward to do -- it's similar to the NJ Rando QR code system. A QR code representing a magic URL, or just the URL itself, different for each control, is given to the control volunteer. The volunteer uses the URL to go to a form that prompts for the rider ID. When entered, that rider ID is checked in at that control at that moment.

Since there is currently no communication from randonneuring.org back to eBrevet regarding check-in status (the phone maintains independent control of the checkin state in the current design), I don't see a quick/easy way to inform the phone that the volunteer has done this checkin. The rider wouldn't know from looking at their phone that this volunteer had checked them in already. They would see no checkin and would NOT receive a finish code or a finish certificate.

With the current system, the FIRST checkin is kept, all additional checkins are ignored. So it wouldn't hurt if both the rider and volunteer checked in.

ctnadovich commented 9 months ago

I see that as a little problematic. The idea of the app is to be a self-contained proof of passage system. If a rider relied on others to "check them in" it would prevent the phone from doing that job -- unless some sort of check-in reverse link was added.

Nevertheless, I see that there would be advantage for volunteers to check-in riders. Perhaps volunteer check-ins could be managed in parallel in some way....

ctnadovich commented 9 months ago

Volunteer check-in would be useful for Secret Controls. Perhaps control-style "secret" should be a thing.

ctnadovich commented 6 months ago

It might be cool to give all riders the power to check-in other riders on the event. For example, the app could have a "roster" page for the event where riders could see the list of their colleagues. This would require the roster and checkins to be published -- if internet is available. Riders could drill down to a control and do a proxy check-in for another rider -- possibly after being granted permission for this from the RBA.