Update reporting level status fields in dashboard.

[ghing]

In order to finish up the functionality described by #25, we need to update the following fields on all elections records:

• Racewide Status
• County Status
• Precinct Status
• CD Status
• State Leg Status

This is a pretty big process. @SaraSchnadt and @ghing should discuss the best way to move forward and look for ways to automate or bulk update.

[SaraSchnadt]

So, I'm working on CA now. If a state, say, has County Level and Precinct level, would you prefer that the other fields are left as "----------" or to qualify further as not available, etc?

[ghing]

All the code cares about is whether the value is "Yes", "Baked Raw" or "Baked", so it won't break anything to leave unset. It also won't hurt if you were to qualify further and that would allow us to present details about unavailable results with a bit more granularity. However, I think you should use your best judgement about current priorities.

Also, as you're doing CA, let me know if you can think of ways that would streamline data entry. Maybe we could update the data, or export as a CSV and bulk import it back in. Let me know if either of those options sounds valuable.

[zstumgoren]

@ghing rather than doing the export/import two-step or writing a batch updater, we should instead add a batch update command to the admin interface for the Elections changelist page. @SaraSchnadt - note that this page already allows editing of these fields (you have to scroll to the far right, so the UI is a little clunky. We could temporarily shift these fields to the left if it helps with editing).

[SaraSchnadt]

are you suggesting batch updating the results availability fields from the
results breakdown field for proofed records? looking over to the right is
OK in this view. As it is now, it's most helpful just to check which
records don't have these fields populated yet.

On Thu, Aug 7, 2014 at 4:24 PM, Serdar Tumgoren notifications@github.com
wrote:

@ghing https://github.com/ghing rather than doing the export/import
two-step or writing a batch updater, we should instead add a batch update
command to the admin interface for the Elections changelist page
http://dashboard.openelections.net/admin/hub/election/. @SaraSchnadt
https://github.com/SaraSchnadt - note that this page already allows
editing of these fields (you have to scroll to the far right, so the UI is
a little clunky. We could temporarily shift these fields to the left if it
helps with editing).

—
Reply to this email directly or view it on GitHub
#31 (comment)
.

Sara Schnadt
Community Liaison/Designer - CensusReporter
Project Manager - OpenElections

CensusReporter.org
OpenElections.net http://blog.openelections.net/
saraschnadt.com
@SaraSchnadt https://twitter.com/SaraSchnadt

[ghing]

@zstumgoren Good point! I forgot about the elections changelist page (I usually look at them through the state detail page).

@SaraSchnadt, I was referring more to a less clunky interface to for updating these fields, but if you feel like there's a way that you're using another field to set the value of the status fields that could be automated, let me know.