Skip to content
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

Convention for linking to raw data that isn't from an official state elections website #177

Open
ghing opened this issue Aug 7, 2014 · 1 comment

Comments

@ghing
Copy link
Contributor

ghing commented Aug 7, 2014

We should decide on a convention for linking to raw data that isn't from an official state elections website. This is needed when we received data on DVD or via email. In many cases, such data is stored in the openelections-data-{abbrev} repos, but not in a particularly standardized way.

The implementation point for this should probably be the Datasource.

This came up when deciding on the best implementation for linking to source data on the front end (see openelections/openelections.github.io#27).

@dwillis
Copy link
Contributor

dwillis commented Aug 10, 2014

I think it depends on the size of the files, but I'd recommend that if we're dealing with individual files (spreadsheets or text files), they be placed in a raw folder in the openelections-data-{abbrev} repo to distinguish them from any necessary pre_processed files (WY is an example of this).

If the file(s) represent all results in a single election (like PA), I think splitting them into office-specific files using our naming convention makes sense. But open to better suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants