Open michelleif opened 5 years ago
New loc_name_batch2.jsp returns n79041965 as rank 1 for a query of "Seattle (Wash.)". Note that the exact name logic is inherently case sensitive if you want it performant...
Did you fix something or you're telling me there's already a way to find Seattle (Wash.)?
@eichmann I don't see this change reflected via sinopia or using the lookup.ld4l.org URL @sfolsom do we want case-sensitive searching? I was expecting case-insensitive
@michelleif it's configured on my end, but awaiting testing and deployment in QA.
NOTE that exact match is case-sensitive.
q=Seattle (Wash.)
has n79041965 as the first resultq=seattle (wash.)
doesn't have n79041965 in the first 50 result :( I see the same results when limited to the geographic subauthority.
Adding example: author search for Kate DiCamillo. First 8 results only include author/title uniform titles for several of her works, and not the NAF heading for her name alone. Relevancy should rank the author name alone first, before any headings for their works if nothing else is entered in the query
Need to write one or more accuracy tests to reflect the desired behavior. @sfolsom Is this something you can do?
Lower case tests, https://github.com/LD4P/qa_server/pull/372
searched for
seattle
in QA cache of LOC Names https://lookup.ld4l.org/authorities/search/linked_data/locnames_ld4l_cache?q=seattleand expect to find this: https://lookup.ld4l.org/authorities/show/linked_data/loc/names/n79041965 for city of seattle but it doesn't appear
it doesn't appear if you search on the full label
seattle (wash.)
either https://lookup.ld4l.org/authorities/search/linked_data/locnames_ld4l_cache?q=seattle+%28wash.%29