Backend - Operator Admin Page - Updating the rider and/or driver list due to unforseen events about voteamerica.github.io HOT 3 OPEN

@stephenscapelliti thanks for these good questions. I'm slightly thinking aloud with this response, so do feel free to challenge anything.

The general thinking behind the original system was that driver/rider would have enough info to contact each other with provided contact details so the situation was for them to resolve outside the system. The system does provide Cancel options on the self-service page for both driver and rider which notify the other person.

The operator/help-line facility existed as back-up to the above, although in practice they were very busy, which suggests not every driver/rider pairing was able to use the above system.

I'm not the originator behind the the revised operator approach, so my views on this that follow are my interpretation (although I think much of the design thoughts are more at the general guideline stage anyway). Given that, the idea seems to be to centralise organisation around the operator, with the operator provided with more system tools to do this.

One benefit of this is to avoid the system having to manage various logins and co-ordination. Although in some ways the new login system could be extended, it is extra complexity that's beyond the midterms. Perhaps something to consider for a later version, though.

One key point at the end of this is how the operator page should display information about cancellations. To some degree, that info exists for drivers with the status field, although currently time info is not shown (that should be added shortly). Similar info should be shown for riders. However, is this sufficient for the operator? I'm not an operator, so I don't know. It wouldn't be so hard to show cancellations for the last hour/day on the operator page, but any contribution means something else isn't done.

from voteamerica.github.io.

Thanks so much for that history, @jkbits1. These were general thoughts about functionality, and it sounds as though they might be beyond the original scope, certainly with regard to the 2020 midterms. Perhaps notification would be something to consider later on. It might help to have input from operators, to determine from their experiences whether this is even worth considering.

from voteamerica.github.io.

A similar (not quite duplicate) discussion is in issue #355

from voteamerica.github.io.