4 ms·
There are google forms that you can setup that populate a spreadsheet. People don't need access to see the spreadsheet. One problem is that you have to authenti
by viggity 7y ago
There are google forms that you can setup that populate a spreadsheet. People don't need access to see the spreadsheet. One problem is that you have to authenticate it is the legit precinct captain, presumably they have some pin/password that they'll enter that is unique to their precinct. You can't prevent people from entering the wrong stuff, you'll have to cull the spreadsheet, but still, it seems pretty damn manageable.
- alpb 7y ago^ this. P.S. I work at Google and internally sheets is used thoroughly to survey large numbers of employees and it can view large sheets for a lot of people in "read-only" mode pretty well.
- adrianmonk 7y agoThat's exactly what I did when I had performance problems. I also had some processing that happened whenever someone submitted a form. I found that I hit a performance limit when many people tried to submit the form in a short period of time. I eventually found that if I changed how the spreadsheet was structured, a lot of problems were drastically reduced. I forget the details, but I think I switched to having one sheet that just collects form submissions and does nothing else, then another sheet that uses Javascript to pull data off the first and do the computations. That way processing was moved offline from form submission. But the general point is, you can't just write a spreadsheet, collect thousands of form submissions, and have no issues. You can't just assume "Google scales everything". N people interacting with N (or 2N or 3N if you share with a few) spreadsheets is an embarrassingly parallel problem. N people interacting with 1 spreadsheet is not.