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

# RE: VIBS Instruction modifications

- To: rcr@dieboldes.com
- Subject: RE: VIBS Instruction modifications
- From: Mark S Earley <meglobal@earthlink.net>
- Date: Mon, 14 Jan 2002 15:49:37 -0500
- In-Reply-To: <PPECJKNKLDJLKJPKPPIOGEIDDFAA.ken@dieboldes.com>
- References: <5.1.0.14.0.20020114135159.00ac77f0@mail.earthlink.net>

OK, that is good. I do not have a keypad to move thru the ballot properly so I can test some of these things out. I am ordering one now.
Mark
At 1/14/2002 03:23 PM, you wrote:

> It already works like that. Apologies if there was confusion to the contrary. VIBS_Welcome.wav is the preamble and does not repeat. VIBS_Instructions.wav repeats when the user presses 0.
> Ken
>   -----Original Message-----
>   From: owner-rcr@dieboldes.com [mailto:owner-rcr@dieboldes.com]On Behalf Of Mark S Earley
>   Sent: Monday, January 14, 2002 11:55 AM
>   To: rcr@dieboldes.com
>   Subject: RE: VIBS Instruction modifications
>   Ken,
>   how much coding changes will be required to split the instructions into an opening portion that does not repeat, and a repeating portion? I think now the entire instruction set repeats.
>   Mark
>   At 1/14/2002 01:21 PM, you wrote:

>   From: owner-rcr@dieboldes.com [mailto:owner-rcr@dieboldes.com]On Behalf Of Mark S Earley
>   Sent: Saturday, January 12, 2002 5:50 PM
>   Examples of possible modifications:
>   1. Opening Instructions (these do not repeat when the 0 key is pressed):
>   2.a. Opening Instructions will be followed immediately by the 0 instructions, which repeat when the 0 is pressed:
>   2.b. Or without the underlined sentence above:
> Feel free to make any modifications to the instructions that you feel are appropriate. This offer has stood for a long time. We are in no way wed to the current text.
> Don't get too carried away with the length of the instructions. Navigating the ballot is supposed to be self-explanatory. We tell the voter at every candidate what each of the valid keys do. Until 4.2.1 and mp3, you will be probably be constrained in the length of instruction audio, or will end with a ridiculously huge TSText.
> Who will do the physical recording for you I don't know, but I'll put them in the standard set on demand. It won't take much to improve what is there.
> Finally, I think the state is stepping out of bounds a bit here if they are dictating the instruction text. This is all customizable. Do we have to go back to state certification if our customer decides they would like a shorter (or longer) instruction text? I think not.
>   3. In response to pressing 5 on an unselected candidate when the race is fully voted, prompt,
> Hmmm. The design for 4.2 is for the unit to beep at the voter when they press an invalid key. I think this is less obtrusive. That said, playing candidates that cannot be voted is a special case for Florida anyway. The rest of the country will turn them off. So maybe this is a special case that deserves an explanation to the voter as to why they are even listening to this candidate.
> I think it will be pretty difficult to come up with a script that is always logically correct though. In the case of a vote-for-more-than-one, it is not "deselect your current choice" but "deselect one of your current choices". In the case that the candidate cannot be voted because of a recall race, the whole sentence doesn't make sense.
> I'll put it in as you have suggested, but I can't promise that it will live into 4.2. A civilized "beep" should suffice to tell the voter that they have don't something wrong.
>   4. As part of the race header, detail the number of candidates in the race.
> This is just a race header audio recording thing. If you want to tell them the number of candidates in the race, feel free. You can even put in recommendations on who to vote for, recent hockey scores, whatever.
>   Items 3 and 4 deal with requested changes, and can be omitted (I guess, who really knows for sure) if they require major code changes.
> Ahh, okay. Please find out whether you require item 3 to pass. I would prefer to let it be and give them the beep in 4.2. Perhaps telling them the beep is in the works for a future release will suffice.
> Ken

- References:
  - RE: VIBS Instruction modifications
    - From: Mark S Earley <meglobal@earthlink.net>
  - RE: VIBS Instruction modifications
    - From: "Ken Clark" <ken@dieboldes.com>

- Prev by Date: RE: VIBS Instruction modifications
- Next by Date: RE: VIBS Write-In Instruction Modifications
- Index(es):
  - Chronological
  - Thread