Answers.Body: <p>On workaround/better solution is to change the format of the value entered by end users so DAMIEN is converted into Damien, and the dedupe rule compares Damien=Damien and all works smoothly.</p>
  
  <p><a href="https://github.com/TechToThePeople/civicrm-normalise" rel="nofollow noreferrer">https://github.com/TechToThePeople/civicrm-normalise</a></p>
  
  <p>X+</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-01-19T16:28:31.637Z
Answers.LastActivityDate: 2017-01-19T16:28:31.637Z
Answers.UserDisplayName: Xavier
Body: <p>In many case, when visitors register to a public event, they use either capital case for or small case for their last name. Therefore, the deduplication engine considers both to be different. Can it be circumvent?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-17T18:58:35.977Z
Comments.Text: I think this is a really good point and that Deduping should be made to be case insensitive - unless someone comes up with some suggestions this may be something that requires financial or development resources to get progressed via the JIRA system
Comments.UserDisplayName: petednz - fuzion
Tags: <civievent><duplicate-contacts>
Title: deduping - case sensitive?
ThreadText: # deduping - case sensitive?
  
  (Asked by: username_0 on 2017-01-17)
  
  In many case, when visitors register to a public event, they use either capital case for or small case for their last name. Therefore, the deduplication engine considers both to be different. Can it be circumvent?
  
  **Tags:** civievent, duplicate-contacts
  
  > **Comments:**
  > **username_1**: I think this is a really good point and that Deduping should be made to be case insensitive - unless someone comes up with some suggestions this may be something that requires financial or development resources to get progressed via the JIRA system  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-01-19. Score: 1
  
  On workaround/better solution is to change the format of the value entered by end users so username_0 is converted into username_0, and the dedupe rule compares username_0=username_0 and all works smoothly.
  
  <https://github.com/TechToThePeople/civicrm-normalise>
  
  X+
  
  
  ---
  
  