-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Washington datasource #145
Comments
I found some issues with dates in the database dump and metadata entries. They are:
I'm going to follow up with Summer and her WA state contact about this. |
I emailed Nick Pharris, Elections Information Specialist of the Elections Division, Office of the Secretary of State to check about the election date discrepancies. I also emailed Suyeon about the metadata questions. |
@ghing Can you note this and other communications with data sources in the FOIALogs on the appropriate state pages dashboard admin? It's useful to have this type of history in a single spot. Thanks! |
@zstumgoren That makes sense. I tried to do this but got a 500 error! Let me know if you want me to try to find the server logs and figure this out. |
@ghing damn. looks like a bug crept in. feel free to poke around the nginx and uwsgi logs if you want to see if there's a quick fix. but let's not get too bogged down in it. can also discuss at scrum. |
@ghing fwiw, this only appears to be triggered by the Log inline entries. I've been adding VA election inlines all week without problems. Also just tested and election inlines still work fine. |
Is there a way I can add a log not as an inline? |
Yep, if we created a free-standing LogAdmin resource and redeployed the On Fri, May 30, 2014 at 1:34 PM, Geoffrey Hing notifications@github.com
|
Cleaned up the dashboard metadata entries I referenced above:
|
First pass at implementing the datasource for Washington state. This requires a url_paths.csv file and a custom fetch class because some precinct-level results are archived in ZIP files. The custom fields in url_paths.csv needed to work around the data quirks are documented in openelex/us/wa/mappings/README.md. PDF results still need to be converted and there are some cases where there are multiple precinct-level files and it is unclear which one to use. Addresses #145
Add a preprocessed URL for Washington State results that are shipped in an Access database to the datasource mappings output. The actual preprocessed result file still needs to be created (see #150), but the datasource and fetch task will be ready to consume it once the preprocessed files are created. Addresses #145
After preprocessing the data (#144), wire it into a datasource.
The text was updated successfully, but these errors were encountered: