-
Notifications
You must be signed in to change notification settings - Fork 3
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
Modify parser to ingest new CSV format #114
Labels
Comments
waldoj
added a commit
that referenced
this issue
Aug 30, 2016
waldoj
added a commit
that referenced
this issue
Oct 26, 2016
Change how we parse and output files, now that we know when one file ends and another one starts. This hasn’t even been tested yet. Toward #114.
waldoj
added a commit
that referenced
this issue
Oct 31, 2016
waldoj
added a commit
that referenced
this issue
Oct 31, 2016
Next up: modify the file iterator so that, instead of ingesting them naively, they are ingested as CSV. Then modify:
to instead strip and rename the field, but otherwise leave it alone. |
Now the problem is that CSV and JSON are both being streamed into a single file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of August 1, the SCC is publishing CSV instead of their gnarly fixed-width format. As of October 31, they will no longer publish the old format. So that provides a 3-month window in which to upgrade Crump to use CSV. That ought to mostly involve simplifying it a great deal.
The text was updated successfully, but these errors were encountered: