An easy way to get all the data in csv

codeforamerica / cityvoice

A place-based call-in system for gathering and sharing community feedback

MIT License

47 stars 35 forks source link

An easy way to get all the data in csv #233

Open jmadans opened 9 years ago

jmadans commented 9 years ago

City partners need an easy way to download all the data from their CityVoice survey. Ideally, they should be able to add /all-data to the end of their instance's URL and then get a spreadsheet with something like the following

/all-data.csv :

Unique ID for each caller
Location
Numerical answers
Timestamp
Link to voice recording (?) - or some way of matching the data to the voice message w/o having to scroll through a location's messages

jmadans commented 8 years ago

Before I close, which PR added in the /export.csv feature? @daguar

daguar commented 8 years ago

@jmadans It wasn't merged as a PR — I believe Mike just cherry-picked my working branch commit onto the current deploys.

@waltz If you want to take a look, it's on the csv-export branch. It could be cleaned up and needs some tests, so feel free to add some commits on top and make a PR if you'd like.

waltz commented 8 years ago

@daguar Neat, I'll take a look at the branch this morning. I was wondering where the CSV work was :+1:

waltz commented 8 years ago

Woof. I didn't remember this thread and goofed big. Here are some links to keep this conversation up to date.

Here's a pull request for export integration specs: https://github.com/codeforamerica/cityvoice/pull/247
A commit with the code that does the exporting: https://github.com/codeforamerica/cityvoice/commit/6a822134e9e3df00dee4e0c19906408d65632405

I think there are two courses of action here:

Merge the specs. Done! Good because it's simple.
Put the specs in csv-export. Remove https://github.com/codeforamerica/cityvoice/commit/6a822134e9e3df00dee4e0c19906408d65632405. Merge csv-export. Rewrites history, but preserves attribution and makes development flow more clear.

Thoughts?

daguar commented 8 years ago

Attribution doesn't matter that much to me — pretty much my main goal is working code with tests on that so you have a :+1: from me for any strategy that achieves that :smile:.

The reason the cherry-picked commit happened is because the builder uses Heroku's platform API which, concomitantly, builds an app from a tarball rather than a git repo, so the history is blank. (In the long run I think if there's an expectation of regularly-updating instances built with the builder then it should be modified to use git to build the customized repo, but that's a broader/puntable question.)

jmadans commented 8 years ago

Hey @waltz, where did we leave this? Will all instances created by the builder now DL all the data when adding /export.csv to the end of the url?