You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Secretariat occasionally gets tickets from django-project@tools.ietf.org with subject lines like "Possible duplicate Person objects for [Name]."
We follow up on these and try to determine whether it's one person with multiple records, or multiple people with the same name.
If it's one person with multiple records, and they have more than one Datatracker username, we ask them which one they'd like to retain before merging the records.
Person 2 Dr. Stephen T. Kent (pk=630)
time: 2012-02-26 00:03 PST
ascii: Dr. Stephen T. Kent
email: kent@bbn.com
aliases: Dr. Stephen T. Kent, Stephen Kent
Would it be possible to add "username" to the list of information provided in the initial tickets to us? That would save us the step of having to go look that up separately. (For records that don't have a username, something like "none" or leaving that blank would be helpful.)
Thank you!
Cindy
Issue migrated from trac:2307 at 2022-03-04 05:52:47 +0000
The text was updated successfully, but these errors were encountered:
Merged in d330b8d from rjsparks@nostrum.com:
Add usernames to the email sent to the secretariat when a possible duplicate person has been detected. Fixes #2307.
resolution_fixed
type_enhancement
| by cmorgan@amsl.comHi there,
The Secretariat occasionally gets tickets from django-project@tools.ietf.org with subject lines like "Possible duplicate Person objects for [Name]."
We follow up on these and try to determine whether it's one person with multiple records, or multiple people with the same name.
If it's one person with multiple records, and they have more than one Datatracker username, we ask them which one they'd like to retain before merging the records.
The tickets we get include information like:
Would it be possible to add "username" to the list of information provided in the initial tickets to us? That would save us the step of having to go look that up separately. (For records that don't have a username, something like "none" or leaving that blank would be helpful.)
Thank you!
Cindy
Issue migrated from trac:2307 at 2022-03-04 05:52:47 +0000
The text was updated successfully, but these errors were encountered: