Revisiting issue of the need for case-insensitive search to reduce server load. NY sponsors are all caps


#1

Hello @james

This topic in API support has now been closed. Has there been any progress on the issue of allowing for a non-case sensitive search? I checked the repo and I didn’t actually see any issues open about case-sensitive queries.

I ask because my voter engagement app is suddenly failing in bill searches for New York because the name case is now all caps (it wasn’t 2 months ago). Note that most states have lower case. The workaround to this will be to ALWAYS have to run a second query if there are no results, which is an obvious hit on your database. Indeed, it may be necessary to do multiple pings for people querying any person by name, essentially doubling the server load. A case-insensitive search would solve this issue.

NY Example
“sponsorships”: [
{
“name”: “LIU”,
“primary”: true,
“person”: null
},

MN Example
“sponsorships”: [
{
“name”: “Grossell”,
“primary”: true,
“person”: null
},

Cheers!


#2

There’s no visible progress on


#3

Nice. Not sure why I couldn’t find it on the repo.

Well, it looks like it will be a double hit on the server. Bummer.