nameTransposition in WC1 API

Hi Expert,

I have some questions about nameTransposition in WC1 API. Please kindly assist. Thank you so much.

How does the nameTransposition work when setting nameTransposition = true in WC1 API? for example, if send name = Emma Watson to WC1. does WC1 will use "Emma Watson" and "Wastom Emma" to do the screening?
Does nameTransposition have any limitations?
Does it need to do following process before sending data to WC1 via API?
- special characters such as ". , ' - / \ ~ ( ) & ^ # < > should be removed. (e.g. Ai-Ai --> AiAi, Noh. Ali --> Noh Ali)
- spaces should be removed (e.g. Gi Gi ==> GiGi, Lau Gi Gi ==> LauGiGi)
- all numeric characters should be removed (e.g. Ai7Gi23 ==> AiGi)
- characters with accents should be replaced and normalized to their accent-free counterpart (e.g. VŨ ĐUC TÂM --> VU DUC TAM)
- all characters to be converted to small case so that case sensitivity will be ignored (e.g. GIGI–> gigi)

Find more posts tagged with

Hi @rebecca.hsieh, Thanks for reaching out to us!

Please find my comments for the queries raised above

Yes, you are correct! For Example: If you are screening a name John Smith Joseph and if you set nameTransposition = true in your request body. WC1 will find all the possible combinations like “John Smith Joseph”, “Smith Joseph John”, “Joseph John Smith” and generate the results.
There is no specific limitations we generally recommend to utilize the nameTransposition feature if you don’t know the order of the name to screen.
No need of following the process which you have mentioned above, but if you're trying to screen names with special characters make sure that you pass the request payload by encoding the request payload as ‘UTF-8’ and then use it to calculate the content length of the payload. This is done to properly calculate the content byte length and not the string length. It’s the length of the content/payload sent to the API which determines that the request will succeed or not, if your request contains special characters. Also, when the payload is being sent in the request, it has to be sent as UTF-8 encoded.

Thanks

Hi @rebecca.hsieh, Thanks for reaching out to us!

Please find my comments for the queries raised above

Yes, you are correct! For Example: If you are screening a name John Smith Joseph and if you set nameTransposition = true in your request body. WC1 will find all the possible combinations like “John Smith Joseph”, “Smith Joseph John”, “Joseph John Smith” and generate the results.
There is no specific limitations we generally recommend to utilize the nameTransposition feature if you don’t know the order of the name to screen.
No need of following the process which you have mentioned above, but if you're trying to screen names with special characters make sure that you pass the request payload by encoding the request payload as ‘UTF-8’ and then use it to calculate the content length of the payload. This is done to properly calculate the content byte length and not the string length. It’s the length of the content/payload sent to the API which determines that the request will succeed or not, if your request contains special characters. Also, when the payload is being sent in the request, it has to be sent as UTF-8 encoded.

Thanks