Normalize the names returned from BankD and GrandID
See original GitHub issueThe name(s) returned from BankID and GrandID seems to be returned as all capital letters in some cases. For me personally, it does not, but fore some colleagues it does.
So, for me it’s returned as this: Peter Örneholm
But for some other, it’s returned like this: PETER ÖRNEHOLM
Should we, and if so how, implement a way of normalizing this in any way? Would be nice to be able to consume it and trust that it’s written not capitalized.
If we decide to implement it, I’d suggest it’s behind a flag so you can disable it from *AuthenticationOptions
.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Normalize human names in postgresql
I am trying to find duplicates. For example, I want to consider O'Reilly a duplicate of oreilly. La Salle should be a duplicate...
Read more >Name normalization
Name normalization analyzes email document headers to identify all aliases, such as proper names, email addresses, and more, and the entities, ...
Read more >related organizations
There is a grandfather provision for certain non- conforming activities of a company that is not now a bank holding company but then...
Read more >Banks and Banking
Each title is divided into chapters which usually bear the name of the issuing agency. Each chapter is further sub- divided into parts...
Read more >Insight into Name Normalization: What Is Your Name?
Assigning a single unique name to identify an individual has created problems that precede the inception of e-discovery.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yea, I think if we can’t make it “good enough” we might skip this for 1.0, and as you say, we could ask whey the data is all cap in the first place. Really strange. I feel implementing it but not supporting a lot of scenarios might only make people confused.
Could
TextInfo.ToTitleCase()
be used? https://docs.microsoft.com/en-us/dotnet/api/system.globalization.textinfo.totitlecase?view=netstandard-2.0We’d have to lowercase everything at first as all capitalized words is ignored.