Manage duplicates during csv import

[StephanieJoly4]

@Bonapara loading here the issues I faced managing duplicates during csv upload for later. We don't necessarily have to manage all of this with the product but I think it's useful to log issues users might face.

PEOPLE

• if one email from the csv to upload already exists in Twenty, the entire upload fail. -> would love to return the lines that failed but to still upload the rest
• not rare that customers give csv to upload that contains duplicated emails (not for us to manage but maybe to help them identify the issue)
• email is currently the key. Do we want to let the user chose another key, for example the linkedin profile ?
• records with similar fields but not exactly the same led to creating duplicates (not on us to fully manage but maybe we could flag the similarity to the user before he moves fwd.
  • similar lkd url: https://www.linkedin.com/profilename and www.linkedin.com/profilename or www.linkedin.com/profilename/
  • similar full names linked to a same company

COMPANY, domain being the key, it's easy to create duplicates for companies who have

• similar linkedin URL
• similar (or exactly the same) name

but either the domain is empty, either this is not the exact same format: https:// or www.domain.com or domain.com/