Tabbie2
Tabbie2 copied to clipboard
chief-nerd
Add some data checking UI/UX features to the results entry page
Apologies for the open ended feature request. I also don't have a dev environment working atm where I can replicate things so I'm adding this with 100% certainty that this already isn't the case and I've misunderstood something.
From having a number of iterations on Tabbycat’s eballot page we’ve tried to identify a number of UX/UI features that can help aid in minimising human error during the ballot entry process, particularly on mobile devices. Again I can’t bring up the exact tabbie interface right now so I’m going by memory on what are some options for improvement:
- Display running totals of both team scores and team margins either on the confirmation page and/or on the initial entry page. This provides another piece of data that can be cross checked against the paper ballots to identify errors (by the adj doing the entry).
- Display running rankings of the teams, ideally color coded, on either the confirmation page and/or the initial entry page. Ideally there would be a 2x2 'matrix’ style layout of the rankings here so that it can be easily compared to the ballot’s layout (which is also presented in the standard 2x2 matrix)
- Optimise the mobile layout’s spacing and sizing so that layout is more compact (easier to see/compare scores across teams) and key information (names, scores) are more prominent.
I could potentially look at some of these in a PR, but it’s not likely that would happen anytime soon. The javascript needed to add these though is quite simple and probably easily added to the existing form. If helpful I can point to some analogous functions used in the tabbycat ballot page. It could also be worth pursuing an shared library or plugin for ballot entry as there are not too many differences between 2 and 4 team formats.
Hey @philipbelesky - Thanks for your input Regarding the 'Display running totals' - I don't like to display any points or speaks if possible as this might influence the judge.
Regarding the 2x2 matrix I think this is a really good input and afaik this was already done in some way. The problem is the available space on mobile. But I am open to new ideas here.
Hmm are we on the same page as to what a running total looks like? What I mean is that in addition to the speaker score inputs for each team (75 and 75) there is also a visible element that updates the resulting team points (ie 150) and resulting team rank relative to other teams (although this should probably only be on the confirmation page).
Is that what you were thinking of? I can't think of how showing team points would influence the judges decision but it does give info that can be used for further cross checks against the paper ballot (often identifying math errors in the process).
On 2 Jan 2017, 15:19 +0100, Jakob [email protected], wrote:
Hey @philipbelesky (https://github.com/philipbelesky) - Thanks for your input Regarding the 'Display running totals' - I don't like to display any points or speaks if possible as this might influence the judge.
Regarding the 2x2 matrix I think this is a really good input and afaik this was already done in some way. The problem is the available space on mobile. But I am open to new ideas here.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (https://github.com/JakobReiter/Tabbie2/issues/38#issuecomment-269978263), or mute the thread (https://github.com/notifications/unsubscribe-auth/AAeRWQxWwxAPMimTv3mgFCibt9xSte__ks5rOQdygaJpZM4LY-bf).
@philipbelesky we had this already. See: https://github.com/JakobReiter/Tabbie2/blob/master/tabbie2.git/frontend/views/result/confirm.php#L41 I think we took it out because it either was a UX/UI issue or it confused people too much ... @rscoates do you remember?
Yeah, the vast VAST majority of discrepancies between the eBallot and the paper ballot are that a judge gives a 76/77 (for example) on the eBallot, and a 77/76 on the other. The totals don't stop that, and, in our experience, actually lead to worse results entry, as judges use Tabbie as a calculator (yes, they are that lazy) when doing totals on the eBallot.
I assume there's a happy medium, but I haven't found one yet.
So if there is an issue with the scores being entered out of order, it might be worth setting speaker order as an explicit step during both the paper ballots and the eballots. Obviously it'll slow things down a little but it may be worth it to heighten correctness. My vague theory on this is that adjudicators have a mental model of that debate that is partly chronological (speaking order) and partly spatial (ie the OG/OO/CG/CO matrix) and having to sometimes flip the speaker order and sometimes not flip the order is an extra mental overhead that leads to score errors. When the order is set before scores are the interface will then always conform to this mental model and the overhead is lessened.
For Tabbycat's eballots we use dropdown menus, but for BP you could just have a simple "reverse" button that swaps the order of the DOM elements. That said this may not be as effective if the paper ballots also don't let you set the speaker order explicitly (by writing them out in the order, rather than just marking the position) as that will then also clash with that mental model as well as making cross-checking easier.
The problem is exactly as you said - the paper ballots are a fixed order, and I'd like to keep it that way (as it helps with judges reading names out / confirming it's the correct people / not having to decipher handwriting), and at the moment, the judge can check the paper against the eBallot as a match. It's, I'd guess, a problem in 3% of ballots per round, so it's only at WUDC that this is actually an issue every round, and I don't think the extra burden on judges is worth it. If you were doing a tournament with only eBallots, it might be something to consider, though.
Cross-posting this thought incase it is also of interest to tabbie: https://github.com/czlee/tabbycat/issues/400