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

Handling Duplicate People #33

Open
mlisle opened this issue Aug 29, 2019 · 2 comments
Open

Handling Duplicate People #33

mlisle opened this issue Aug 29, 2019 · 2 comments
Labels
enhancement New feature or request Needs Discussion

Comments

@mlisle
Copy link

mlisle commented Aug 29, 2019

Here's a scenario:

  1. A year ago, Yakut signed up for a blockcert using [email protected]
  2. Today, she signed up for a different blockcert using [email protected]
  3. The admin app kicked off a new email to her, assuming this was a different person.

I don't know the answer to this problem, but it's going to happen alot. Is there a way for us to avoid duplicate records for the same person?

@mlisle mlisle added the enhancement New feature or request label Aug 29, 2019
@stuartf
Copy link
Contributor

stuartf commented Sep 6, 2019

I don't think we can. We can somewhat avoid it by using csv upload and/or #25. Additionally going through the add issuer workflow again shouldn't break anything. We could maybe do something where the user can merge their own accounts by clicking a link in each, but that seems like a pain.

@eareese
Copy link
Contributor

eareese commented Sep 12, 2019

Agreed, I don't think we can prevent this without using something like CAS as an external source of truth. The closest thing I can think of would be to collect and verify user phone numbers, but that would have its own downsides/edge cases.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Needs Discussion
Projects
None yet
Development

No branches or pull requests

3 participants