Skip to content
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.

csv exports include too much #18

Open
TPei opened this issue Mar 7, 2016 · 3 comments
Open

csv exports include too much #18

TPei opened this issue Mar 7, 2016 · 3 comments

Comments

@TPei
Copy link
Contributor

TPei commented Mar 7, 2016

CSV exports include the following fields :id, :created_at, :updated_at, :publishing_consent. I think those should be exlcluded

@berlintam
Copy link
Contributor

thanks @TPei ! I think you're right here. Go for it.

@sareg0
Copy link

sareg0 commented Jan 31, 2017

I'm not sure why we are having a CSV download. What is the reason? I thought it might be not so great for someone to download the data from the database, but only be able to see a subset. This leads me to some thoughts on making the app only an API for people who are working on the front end... This is to protect it, and make sure people can only do particular things with it, because we only give them particular endpoints to take advantage of, that returns a particular set of data.

And here is another particular for good measure 🗡

@berlintam
Copy link
Contributor

I think the original idea behind a csv was so that we could share the data with others somehow. It was a first step towards making the data open to others. Next step would maybe be a graph or something.... Because without the csv the only way to see the data is via our 'stories', which aren't as readable, searchable.

Granted, yes, this can maybe be deleted in the future, but I think a csv is always helpful in some way. If you think there's some data included in there that shouldn't be, we can always discuss taking it out.

Make sense?

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

No branches or pull requests

3 participants