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

Proposal: ask more information on User Export #98

Closed
cmitz opened this issue Dec 4, 2019 · 3 comments · Fixed by csvalpha/amber-ui#72
Closed

Proposal: ask more information on User Export #98

cmitz opened this issue Dec 4, 2019 · 3 comments · Fixed by csvalpha/amber-ui#72

Comments

@cmitz
Copy link
Contributor

cmitz commented Dec 4, 2019

Right now the export UI looks like this:
afbeelding

But I'd like to add one field:

When will you delete this export?

With a placeholder:

I will delete this export 2 weeks after the activity on the 12nd of this month.

Or something like that

Motivation

At the moment I still have a lot of questions when I see a database export email to privacy@. Most of the times the description is not very clear, and there has never been anyone that mentioned how long they will keep it. Asking for when it will be deleted forces a user to think of this.

When working on the screen anyway, we might rephrase the wording of the "Reason of the export" to provoke a more detailed description that is clear for everyone, also people not in the loop of the activities (like me).

@Matthijsy
Copy link
Contributor

I agree with this issue. However I think that we do not need to add another field. We can probably just make more clear what we expect in the 'reason' field. This can also include the date of removal.

We should maybe let the user ask the following questions:

  • Who is going to access the data
  • Why is the data needed (maybe still too broad)
  • How will the data be stored
  • When will the data be removed

@cmitz
Copy link
Contributor Author

cmitz commented Dec 4, 2019

Okay, the form factor is open for discussion. Maybe another field is not required.

The questions, I agree with very much.

Why is the data needed (maybe still too broad)

Could be "What do you have to do, that you cannot do without this data?"

@Matthijsy
Copy link
Contributor

Fixed in UI

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

Successfully merging a pull request may close this issue.

2 participants