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

Make log and report data screen less technical #13005

Closed
tsteur opened this issue May 29, 2018 · 3 comments
Closed

Make log and report data screen less technical #13005

tsteur opened this issue May 29, 2018 · 3 comments
Assignees
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement.
Milestone

Comments

@tsteur
Copy link
Member

tsteur commented May 29, 2018

Delete old visitor logs

image

  • Can we change the title to eg "raw data"?
  • and instead of saying from which tables the data will be deleted, we could maybe explain what raw data is and what it impacts? Eg visitor log and segments?

Delete old archived data

image

  • Can we instead of "archived data" say "aggregated report data" for example?
  • Can we allow even to delete reports after 2 or even 1 month instead of having to keep them for at least 3 which is maybe a bit random? Like why is it 3? I presume 2 might work as well?
  • Instead of writing Data from the database numeric archive tables (archive_numeric_*) and blob archive tables (archive_blob_*) will be deleted. in both help texts can we explain what aggregated report data is etc and not mention DB tables?
  • Can we maybe remove "If enabled, old reports will be deleted. We recommend to enable only when your database space is limited. " as they might also want to remove it for GDPR and privacy reasons etc? Also the database space message and in general all DB messages etc might not be as useful on the cloud...
  • The sentence seems bit random and hard to understand (still not quite sure what the sentence is trying to say) If you have not enabled "Regularly delete old visitor logs from the database", old reports will be recreated automatically when requested
  • Maybe this sentence could explain that only older data past the configured dates will be deleted? If you have enabled "Regularly delete old visitor logs from the database", the data will be permanently lost. The sentence is also a bit hard to understand.
@tsteur tsteur added Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement. c: Usability For issues that let users achieve a defined goal more effectively or efficiently. labels May 29, 2018
@tsteur tsteur added this to the 3.6.0 milestone May 29, 2018
@mattab
Copy link
Member

mattab commented Jun 25, 2018

Agreed with the renaming points above 👍

More feedback:

Can we allow even to delete reports after 2 or even 1 month instead of having to keep them for at least 3 which is maybe a bit random? Like why is it 3? I presume 2 might work as well?

it's a bit random but the idea is to prevent people from deleting everything, as no one ever wanted to delete all reports less than 3 months old (it's wasn't a use case so far). Deleting all data removes a lot of value from Matomo. Sometimes users need to reset their data (and would like to delete it all once), but i've not heard so far of users wanting to delete such recent data.
But we can change the 3 months to 1 month (no strong preference).

The sentence seems bit random and hard to understand (still not quite sure what the sentence is trying to say) If you have not enabled "Regularly delete old visitor logs from the database", old reports will be recreated automatically when requested

It was trying to say "if you delete old reports, they may be re-processed again from your RAW data when you request them". This sentence can be removed I think.

If you have enabled "Regularly delete old visitor logs from the database", the data will be permanently lost. The sentence is also a bit hard to understand.

It's trying to say that if you have also enabled "Regularly delete old raw data from the database", then the reports data you're deleting will be permanently lost. Whereas if you keep the old raw data, then you can manage to re-process the reports data that is being deleted.

@diosmosis
Copy link
Member

@tsteur was this fixed completely in #13464?

@tsteur
Copy link
Member Author

tsteur commented Dec 31, 2018

Yes 👍

@tsteur tsteur closed this as completed Dec 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. Help wanted Beginner friendly issues or issues where we'd highly appreciate community's help and involvement.
Projects
None yet
Development

No branches or pull requests

3 participants