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 'Request correction' link to People pages #708

philosophicles opened this issue Jul 26, 2019 · 0 comments


Copy link

commented Jul 26, 2019

Not 100% convinced this is a good idea, throwing out for feedback.

We could add a small, static text link on each Person page, something like "Request corrections to this information". (Or "Is this information incorrect?", or variations in that ballpark.)

This would go to a new, single-use contact form page, where the site visitor (who isn't necessarily the Person concerned!) can write what's wrong, add email address if not signed in (or perhaps they have to sign in first), and Submit. This page would mostly copy our existing Contact Us page design and validation logic.

Benefit for the site visitor is that, when they see an error on the Person page (name misspelling etc), it's more immediately obvious where to click to solve it, and that we are willing to solve it (in a general sense, as required by GDPR etc). Without this, they have to click around our FAQ and Contact Us pages to understand how to get the correction.

Benefits for us:

  • better compliance with the spirit of GDPR, making it easier for people to control their information
  • We could pre-populate information about which person page / entity this is
  • we could tailor the form fields to make it really clear what information they must supply - since I know we do get some name-change requests where we have to reply back to clarify what name they actually want shown.
  • we could also include information about how we process these requests, if we wanted
  • submissions from this form could be auto-tagged in our support system, and potentially handled differently in some way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.