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

Data should be stored differently at different steps of the process #16

Closed
tpoisot opened this issue Feb 20, 2015 · 3 comments
Closed

Comments

@tpoisot
Copy link
Collaborator

tpoisot commented Feb 20, 2015

Basically, the format for long-term archival is not the same format that is needed for day-to-day analysis. I'd say that in the opposite direction, actually: don't archive your data in the format that makes sense for you in your day-to-day use.

@jhollist
Copy link
Collaborator

👍 I was going to to add something similar, but you beat me to it @tpoisot !

This general idea is captured in the discussion in swcarpentry/DEPRECATED-site#797. Another tangent to this is the idea that not all data are created equal wrt accessibility (i.e. Personally Identifiable Information, Conf. Business Info, etc.) I don't personally work with this type of data so someone else should probably chime in. Perhaps that should be another rule?

@PBarmby
Copy link
Collaborator

PBarmby commented Feb 20, 2015

See also the second ref in #3 for some comments re: different formats for different usage.

@emhart
Copy link
Owner

emhart commented Feb 24, 2015

@tpoisot Could you share a use case here? Are you thinking that it might be archived as plain text but you'd want to access it in a SQL database?

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

4 participants