API does not show drop boxes

[GoogleCodeExporter]

Washington state's feed now has early_vote_site elements. Please incorporate by:

1) linking address->precinct->locality (which you'll have to do anyway to 
incorporate county election administration info)

2) databasing the early_vote_site elements (including optional descriptor 
fields, since WA has used those), which link to locality.

Note: for future planning states can also get from an address to an early vote 
site by address->precinct->locality->early_vote_site or 
address->precinct->early_vote_site ... if either of those paths are present 
(they are not in WA) then you should default to the above

Original issue reported on code.google.com by aaro...@gmail.com on 23 Oct 2010 at 1:29

[GoogleCodeExporter]

The future part seems, err, complicated.
I would designate that if one path is present, they both should be, or just 
designate that it gets set on precinct and that's that.
Otherwise you are talking about multiple extra table joins just to see if an id 
exists.
Additionally, things like "If the precinct is mail-only and the 
early_vote_site_id field is missing then the implementation is required to 
assume that any early_vote_site objects within the same locality are valid drop 
locations for this precinct." are not great spec behavior.

Honestly, error behavior should never direct people to the wrong place, as this 
could if in fact, they are not valid drop locations for this precinct, and 
someone just forgot an id.
That is why the ignored behavior was designated originally on the elements it 
was designated, because saying "i don't know" is preferable to saying "here's 
something, hope it works!"

Original comment by dan...@google.com on 23 Oct 2010 at 2:13

• Changed state: Accepted

[GoogleCodeExporter]

We'll talk about this post-election, but the basic problem is that states link 
counties to drop-boxes/early-vote centers (or vice versa) and often leave 
precincts out of it. Maybe I'll kill the precinct paths next spec -- we'll do a 
canvass of states to see if that would cause issues.

Given that likely outcome, focus on the locality path right now. Thanks!

Original comment by aaro...@gmail.com on 23 Oct 2010 at 1:50

[GoogleCodeExporter]

This is now high priority...we need to give CO a place for their early vote 
centers and distinguish them from vote locations.  See here (in the gadget):

951 B St Greeley CO

Vote Centers (VCs) and Early Vote Centers (EVCs) are mixed together. This will 
be very bad on 11/2 an we need to give CO incentive to fix this before 11/2.

Original comment by aaro...@gmail.com on 26 Oct 2010 at 11:06

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This will not happen in time. What is the safest alternative?

Original comment by gh...@google.com on 27 Oct 2010 at 12:09

[GoogleCodeExporter]

Tell CO to remove EVCs from their feed next Monday? Jared -- can you coordinate 
with them?

Original comment by aaro...@gmail.com on 27 Oct 2010 at 12:48

• Changed state: WontFix

[GoogleCodeExporter]

I would prefer Google tell them if possible.  It puts in a weird place to be 
advocating that people put things in feeds and then take them out later.  

Original comment by anthea.w...@gmail.com on 27 Oct 2010 at 1:22

[GoogleCodeExporter]

Just so we are on the same page, you told them to put the early vote centers 
where the official polling locations are supposed to go?
That seems, uh, strange.

Original comment by dan...@google.com on 27 Oct 2010 at 2:06

[GoogleCodeExporter]

Well, if we told them to put in the EVCs the proper location, they wouldn't 
have shown up on the gadget. (I actually was under the impression that CO 
figured this out for themselves.) I think election officials will understand 
that removing their EVCs from the feed right as their EVCs are closing makes a 
lot of sense.

Original comment by aaro...@gmail.com on 27 Oct 2010 at 2:12