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

Add a full data portability feature #4062

Open
4 tasks
Tracked by #4024 ...
teolemon opened this issue Jun 2, 2023 · 9 comments
Open
4 tasks
Tracked by #4024 ...

Add a full data portability feature #4062

teolemon opened this issue Jun 2, 2023 · 9 comments

Comments

@teolemon
Copy link
Member

teolemon commented Jun 2, 2023

Add a full data portability feature

Tasks

Preview Give feedback
  1. ⭐ top issue User lists good first issue lists 🎯 P1
  • Notification on successful export to open the file
  • Notification action button to share the file
  • Filename should be clear scan-history.csv, shopping-list.csv with a timestamp of export to avoid overwriting older exports
  • product_name, brand, barcode, timestamp of last scan, last access if applicable

Why

  • Outstanding GDPR compliance
  • Being more helpful with lists

Part of

@teolemon teolemon changed the title Turn Export History to clipboard into a full data portability feature Add a full data portability feature Jun 2, 2023
@g123k
Copy link
Collaborator

g123k commented Jun 15, 2023

Is-there a standard for this kind of data?
Or can we do whatever we want?

@teolemon
Copy link
Member Author

We can do whatever we want. Heck, we could even create a standard for food scan histories ;-)

@monsieurtanuki
Copy link
Contributor

After the wikipedia, we could be the Braille or the Morse of food! πŸŽ‰

Just checking: for us, a barcode is only digits?

@g123k
Copy link
Collaborator

g123k commented Jun 16, 2023

After the wikipedia, we could be the Braille or the Morse of food! πŸŽ‰

Just checking: for us, a barcode is only digits?

Yes, barcodes are only numbers-based, as EAN stands for European Article Numbering

In parallel, I've checked schema.org and I think that using the Product type might be interesting in our case: https://schema.org/Product

@teolemon
Copy link
Member Author

do we dump product data, or just the lists of EANs + timestamp ?

Note that we are the defacto standard, and that no one else is really implementing anything at this point.
If we were to dump without thought, what's the list of fields?
Also, there's a way to generate CSVs from the website

@g123k
Copy link
Collaborator

g123k commented Jun 16, 2023

If we want to be retro-compatible with the old Android app (I have to check for iOS), only 3 fields are exported in a CSV:

  • Barcode
  • Name
  • Brand

@g123k
Copy link
Collaborator

g123k commented Nov 6, 2024

@teolemon
Copy link
Member Author

teolemon commented Nov 7, 2024

We certainly can and should. Is there a way to get backup consent ?
It would be a way to stress that we don't save your personal data to the OFF servers.
We would also need a stupid db dump to the phone memory for F-Droid

@g123k
Copy link
Collaborator

g123k commented Nov 7, 2024

We certainly can and should. Is there a way to get backup consent ? It would be a way to stress that we don't save your personal data to the OFF servers. We would also need a stupid db dump to the phone memory for F-Droid

We could ask for consent the first time the user creates a list.
But yes, F-Droid is still an issue here and in that case, the basic import/export by CSV would do the job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: πŸ’¬ To discuss and validate
Development

No branches or pull requests

4 participants