[Date Prev][Date Next] [Chronological] [Thread] [Top]

# Re: GEMS 1.11.2 preference voting errors

- To: "Guy Lancaster" <glanca@dieboldes.com>, "Bug Tracking" <bugtrack@dieboldes.com>
- Subject: Re: GEMS 1.11.2 preference voting errors
- From: "Tyler" <tyler@dieboldes.com>
- Date: Fri, 3 Sep 1999 13:50:15 -0500

I can confirm that a GEMS database with write-in option set to override counts a "vote for one" race as being an overvote if both a named candidate and the write-in space are marked. Edgecombe County, NC observed the same thing and brought it to my attention. As my previous message stated, both Edgecombe and I were of the opinion that setting the write-in option to override in the aforementioned example should have given the vote to the write-in space.
Tyler

> -----Original Message-----
> From: Guy Lancaster <glanca@dieboldes.com>
> To: Bug Tracking <bugtrack@dieboldes.com>
> Date: Friday, September 03, 1999 1:24 PM
> Subject: Re: GEMS 1.11.2 preference voting errors
> Sorry but I was wrong in saying that the Accu-Vote would reject an overvote before checking write-in overrides. Upon checking the code, all write-in override options are applied before the overvote condition is checked as per requirements.

> This discussion was started by Nel's bug report:

> > > > - A candidate and write-in selected in a vote for one race are returned as overvoted, even though the override write-in rule should effect the selection of the write-in only.

> > - Candidacies marked with a candidate as well as a write-in are being tallied as overvoted even though they should be tallied as write-in using the override write-in rule.

> which I believe was in error. Does anyone have confirmation of this behavior?

> Guy

- Prev by Date: RE: GEMS 1.11.2 preference voting errors
- Next by Date: Re: GEMS 1.11.2 preference voting errors
- Index(es):
  - Chronological
  - Thread