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

Which data should be permanently stored in data base #60

Closed
redfrexx opened this issue Oct 19, 2021 · 0 comments
Closed

Which data should be permanently stored in data base #60

redfrexx opened this issue Oct 19, 2021 · 0 comments
Labels
research Stuff that has to be researched and organized. Not as technicall as coding itself.

Comments

@redfrexx
Copy link
Member

redfrexx commented Oct 19, 2021

We need to decide which data provided by the user should be stored permanently in the database and which should be discarded right after the co2 emissions have been calculated.

From a data pricavacy perspective, we should try to store as less data as possible. On the other side it would be good to retrain enough information in case some of the formulas of the co2calculator package change over time (e.g. the completness score co2calculator #48). Or if we want to allow the user to edit some of their data entries after submitting them (e.g. if they made a mistake, should they be able to edit the entry or delete it and create a new one?)

The data which needs to be provided by the user is describe in https://github.com/pledge4future/WePledge/blob/dev/backend/docs/graphql_add_data_queries.md

@redfrexx redfrexx added the research Stuff that has to be researched and organized. Not as technicall as coding itself. label Oct 19, 2021
@redfrexx redfrexx changed the title Decide which data entries should be editable by the user Which data should be permanently stored in data base Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research Stuff that has to be researched and organized. Not as technicall as coding itself.
Projects
None yet
Development

No branches or pull requests

1 participant