-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
People names are not diacritic neutral when adding them from Document Detail page #1479
Comments
#1499 is the same; I'll copy Ksenia's comment here and close: Is your feature request related to a problem? Please describe. Describe the solution you'd like |
…utral-autocomplete Unaccented autocomplete in forms for related entities (#1479)
@blms works well, thank you! Closing! |
Reopening as it works from autocomplete, but not on admin search pages. |
Allow diacritic-insensitive searching in admin list views for People/Places (#1479)
@blms weirdness noted, searching "Elhanan" (no diacritics) gives me 3 results, but searching "Elḥanan" only gives me 2 even though all 3 of those results have Elḥanan in them. Likewise, for the Places pages, diacritic search also gives you less options in the dropdown than non-diacritic search: |
@kseniaryzhova Actually, I think that is a data issue; there is something different about the way those two names are spelled with diacritics. Try copying these two and trying them separately:
|
On the plus side, that means that the diacritic-less search will find even tiny unnoticeable variants like this :) |
@blms data entry problem, as you said! Closing and thank you! |
testing notes (QA) -- round two
In the QA site admin:
testing notes (QA)
In the QA site admin:
'
andʿ
being treated the same—just diacriticsDescribe the bug
While we've made the search results of the website diacritc-mark neutral (i.e. you can search for "Masliah" to get "Maṣliaḥ") the same is not currently true when adding People in the Document Detail page. This will create problems and potentially duplicates of People by making it harder for RAs to attach the correct people to documents.
Screenshots/To produce bug
If I type in "Ma" I get the following results, but if I type in "Mas" without the underdot, the results don't populate:
Expected behavior
Underdots, macrons, and the hamza/ayin notations should be ignored when typing a name to pull up an existing person (i.e. use the same logic developed for the frontend).
The text was updated successfully, but these errors were encountered: