Add dev volunteer names

openelections / openelections.github.io

Entry point into Openelections project status and data

MIT License

12 stars 11 forks source link

Add dev volunteer names #22

Closed ghing closed 10 years ago

ghing commented 10 years ago

Add dev volunteer names to summary box in top right on data view too (like on metadata view).

One challenge with this is that the most up-to-date version of the dev volunteer list is not stored in the dashboard. It's stored in a Google Spreadsheet.

The data model for the dashboard supports identifying someone as a dev volunteer, but doesn't support defining relationships that specify a volunteer, role and state. So, it might be hard to accurately represent a volunteer's relationship with a state in the case where a volunteer is both a dev and a metadata volunteer, is involved with different states, or has different roles in different states.

@SaraSchnadt can you offer any insight into how frequent these cases are?

The tradeoff between pulling this data from the Google sheet vs. the dashboard is the same as https://github.com/openelections/openelections.github.io/issues/19

ghing commented 10 years ago

I've uploaded a flattened version of the volunteers in the dashboard to https://docs.google.com/spreadsheets/d/1sr4eejTOpDVbdYFIMDfa3f_ks1iJsgK1itFMnmglVjY/edit#gid=283562565. This might be a good way to figure out how out of sync the dashboard and the dev tracking spreadsheets are and whether or not the data model is to ambiguous to represent volunteers the way we want to.

dwillis commented 10 years ago

Looks like there are some cases where the dashboard is out of sync, but I think they could be handled.

ghing commented 10 years ago

My big questions, probably best answered by @SaraSchnadt are:

Is it a reasonable amount of work to update the dashboard records by hand, or is it onerous enough that we should generate this from the dev spreadsheet or do some kind of bulk update script?
In aligning the dashboard with the spreadsheet, are we losing some kind of historical tracking data that we'd like to keep?
Are there situations that would be confusing if we generated the data from the dashboard?
- e.g. Volunteers who have different roles in different states.

@SaraSchnadt, can you review and then assign this back to me with some answers. Thanks!

SaraSchnadt commented 10 years ago

Hi @ghing, here are my thoughts on this.

Is it a reasonable amount of work to update the dashboard records by hand, or is it onerous enough that we should generate this from the dev spreadsheet or do some kind of bulk update script?

Since we have far fewer dev volunteers than metadata volunteers, it's OK to update this by hand. I can do this.

In aligning the dashboard with the spreadsheet, are we losing some kind of historical tracking data that we'd like to keep?

No

Are there situations that would be confusing if we generated the data from the dashboard? e.g. Volunteers who have different roles in different states.

I think it's fine if the user sees the same name in a different role for meta data and data views.

ghing commented 10 years ago

It seems like it makes sense to generate these values from the dashboard.

ghing commented 10 years ago

This is done. We still have to update the dashboard entries to reflect the current reality (see #40).