Create a "profile" control for changing a person's name

[leovegoda]

Is your feature request related to a problem? Please describe.
It is not possible to change a person's given name in PeeringDB. People change names for a variety of legitimate reasons, including marriage. PeeringDB should create a control allowing users to adjust the name listed in PeeringDB so it reflects records at affiliated organizations and elsewhere.

Who is affected by the problem?
PeeringDB users.

What is the impact?

• Help organization admins when they reconcile a list of current users against a list of current people in their organization.
• Help people who have changed their name feel recognized.

Are there security concerns?
No.

Are there privacy concerns?
No.

Describe the solution you'd like

1. Show the current person name in https://www.peeringdb.com/profile
2. Add an edit button, allowing a person to change the name.
3. Have a single text field where a person can put their new name.
4. Show users a dialogue stating that they are about the change from OLD NAME to NEW NAME with a Cancel option on the left and an OK option on the right.
5. Confirm the name change in a message sent to the primary address of the user's profile.

Consider whether the confirmation should also be sent to the Admins of organizations the user is affiliated with.

Do you think this feature will require a formal design?
Maybe.

Describe alternatives you've considered
Do nothing.

Could this feature request need support from the Admin Committee?
Unlikely. This feature request is being created because the Admin Committee noted that this is not possible when resolving a support request.

What is the proposed priority?
To be discussed.

Provide a rationale for any/all of the above
We should help our users and the organizations they work for reflect currently used names in PeeringDB to avoid confusion and upset.

Additional context
In the support issue, the user did not have a second name registered but the Oauth application required one. The user could not authenticate.

[ankeshanand1]

+1

[jackcarrozzo]

+1

[arnoldnipper]

+1

[tcsweetser]

+1

Will ID be required in the business process?

[netravnen]

Tag @peeringdb/ac

[netravnen]

Consider whether the confirmation should also be sent to the Admins of organizations the user is affiliated with.

Personally, I think this SHOULD be changed to "both members and admins" of all organizations the user is affiliated with at the point in time of the name change takes place. --> This is to allow other organization members and admins to know about name changes of shared accounts, too. Even if we (PeeringDB) want to do away with shared accounts. Some/Many organizations will still setup shared accounts despite our best intentions.

Apart from the above. I do agree with the proposal in its entirety.

[peterhelmenstine]

+1

[leovegoda]

Consider whether the confirmation should also be sent to the Admins of organizations the user is affiliated with.

Personally, I think this SHOULD be changed to "both members and admins" of all organizations the user is affiliated with at the point in time of the name change takes place. --> This is to allow other organization members and admins to know about name changes of shared accounts, too. Even if we (PeeringDB) want to do away with shared accounts. Some/Many organizations will still setup shared accounts despite our best intentions.

Apart from the above. I do agree with the proposal in its entirety.

Perhaps we should just create a per-organization control for this? Some organizations will want that visibility and others won't. We can just let them choose. We should probably default to more targeted notifications. Send too many and people tune out.

[netravnen]

Perhaps we should just create a per-organization control for this? Some organizations will want that visibility and others won't. We can just let them choose. We should probably default to more targeted notifications. Send too many and people tune out.

Very much true. 👍

[leovegoda]

Summary

1. Show the current person name in https://www.peeringdb.com/profile
2. Add an edit button, allowing a person to change the name.
3. Have a single text field where a person can put their new name.
4. Show users a dialogue stating that they are about the change from OLD NAME to NEW NAME with a Cancel option on the left and an OK option on the right.
5. In https://www.peeringdb.com/org/NNNNN#users add a table "Name changes for affiliated users" and only show entries if affiliated users change their name
6. If a user changes their name add a row with columns for username, current full name, previous full name
7. Under the "Name changes for affiliated users" add a control with three options: No notifications (default), Notify admins of new entries in this table, Notify all affiliated users of all entries in this table.
8. Notifications should have a Subject of "PeeringDB: Affiliated user has changed name" and should have a body noting the username, the previous chosen name, and the new chosen name. It should also include a link to https://www.peeringdb.com/org/NNNNN#users