First, you can definitely have an existing member register multiple times for an event, this is by design. Lots of clubs do this but it must be in a different class and/or car number.
Sure, I understand that, and we get it too. What I'm referring to is an identical copy of the same driver, same car, same class, same number. I'm not even saying that shouldn't be allowed - I'm just saying it would be nice if the system warned you when you were making an identical dupe.
There was a bug, that allowed only the same member to be registered with the same class and car #. that was fixed in 2.3.6.
OK, that sounds like what I am talking about. So this is a bug in the current version that is fixed in the next release? Awesome.
It sounds like your duplicates are happening because your registrars are double clicking the Save button when registering from the Lookup and/or creating new driver's when they shouldn't be. The former is prevented with 2.3.6 but wouldn't hurt to educate the people that a web page button is a single click. The latter is prevented with 2.3.6, but you really shouldn't be needing it.
No, I don't believe they are, because last week I went to the online demo and added 4 or 5 copies of a driver named Adam Coolidge to one of the events. It appears to have been overwritten now, but he was entered at least 4 times with identical name, car, number, and class, and even run group. Apparently the demo software has been updated, because I just tried to do it tonight, and it would not create dupes.
I'm not there during your event's but I'm not sure I understand your process.
Why does a driver not know if they have pre-registered or not?
Why does a driver not know if they have gone through the registration process already?
The original interface was really designed around medium to large clubs. There would be 1 line for pre reg and another for walkups. Pre reg line uses the Driver Checkin while walkups use Registration screen.
We typically have 70-75 cars per event. Here's what we do:
We have a small information card for each driver at each event. Once MSR prereg closes before the event day, we export the MSR data to a CSV file that is then mail-merged into a Word table doc to create a preprinted card for the preregistered drivers. We also make a stack of blank cards for walkups.
At the event, everybody goes to Line 1. Preregs are given their cards to check. If all info is good, they take the card and proceed directly to tech. If there are changes, they are told to mark them up and go to Line 2. Walkups are handed a blank card and a pen and directed to go to Line 2 after filling out their info.
Line 2 has a laptop open to the Registrar screen. Each driver gives their completed card to the registrar, who uses Lookup to see if the driver exists in the database. If so, they make any changes necessary and Save the driver to the event. If an all new driver, they use New to create a new member entry, then Create. The driver is handed back their card and directed to tech. Car is teched and inspector initials card. If savvy and within wireless range, they will also mark driver as teched via TI screen.
After tech, all drivers return to Station 3 where they pay, are assigned a run group and work station, and hand in their card. Group and station are noted on card. We have a binder full of tearoffs that sequentially assign stations - appropriate tearoff is given to driver.
As time permits, completed cards are gathered and divvied up among available computers to be finalized in the system via the Driver Checkin screen. Any leftovers are checked in during the drivers meeting. Cards are filed for record. Once the drivers meeting is over, we open a session / run group, and start queuing cars as they grid up.
We stuck with the card system (though they are half the size because they don't hold run information any more) because it provides redundancy in case of system failure, without a ton of duplicated effort. It also means that not all volunteers need to have a computer or even know how to use one. Line 1, for instance, and Line 3 do not need a device and they can be handled by old school members who do not take well to technology. Ditto the TI position.
We also manually record times and cones on worksheets, as well as having the TK and CC managing them in the AXti.me system. More than once we were able to easily keep the cars running when we fixed queuing issues or timing burps, just by checking posted times against the manual version to make sure the sequencing in the system was correct.
I know this is theoretically a paperless RM program, but I don't see that happening until I can keep the entire network up all day with no hiccups, and I have half a dozen people who are fast and fluid at using the role system.
Brandywine Motorsport Club Autocross Chair
AXti.me user since 02 April 2015