You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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).
The text was updated successfully, but these errors were encountered: