Handling of special characters in last name comparison
Description
#14 (closed) deals with making sure last name comparisons are case insensitive but the current Jackdaw version does some handling of special characters. The prime example be names with hyphens and non-ASCII characters.
For Refinement
We need to decide what level of extra checking/comparison we want to do for this (hopefully less used) part of the flow.
We need to consider names like: García, François, Sørensen, Björnsson, Nguyễn, as they aren't uncommon and we should be aware of them.
Our decision, for MVP release, is that we will match current functionality of jackdaw, which does a comparison that the entered last name matches the "first part" of the name field.
Further details
Task list
- Update authentication check to match decided last name check
- E.g. matches
<user entered last name> .* - Blank entry is rejected
- E.g. matches
- This change is to match current checks against jackdaw, and is not expected to be guaranteed to "work" against all users in production/test databases - as we expect this is not the case for the current version of the service in Jackdaw.
Acceptance criteria
-
Last name check is updated to work as agreed
Links/references
Edited by Robin Goodall