RE: [RC] rm software - David LeBlancIt's not that hard to do if you use a real database as a
back-end. It could be done more easily in Excel even if it were programmed
correctly. What you do is have a table (or sheet in Excel) just for riders, and
one of the properties of a rider is the distance.
What needs to be done to do this right
is:
1) Provide access to the rider database via web
front-end
2) The RM then connects to the front-end with the app. One
tricky part is making sure that everyone else on the Internet can't also
get to the rider database.
3) A little while later (this would have to be tested to
see just how long), the RM has the current rider database.
4) Instead of keying in everything about the rider, the RM
then just enters the rider number (if present), and all the rider info comes up.
If it looks like the right person, great. If not, then you have to search by
name, or enter new rider. Same system for horses.
5) You then enter ride times for each rider, and it figures
out everything.
6) Once you're done, you then print out the results in case
something goes wrong, use the app to connect back to AERC, and upload the
results.
7) AERC home office then does whatever they feel like they
need to do to validate the information, and another app updates the main
database with the ride results. This part is also tricky because we want to be
sure that we're not updating some other ride.
This _can_ all be done - it's a SMOP (Simple Matter of
Programming). Depending on the skill of the programmer, you're probably looking
at 80-160 hours of programming and testing. IMHO, we ought to do this - it would
save a lot of RM time, and perhaps more importantly, time spent at the home
office transcribing things. Most of the problems with the current software isn't
a problem with software, it's that this software isn't user-friendly
enough.
|