Problems with new search v2.0
Well it seems we have some issues with the new search – for example it stopped working today at 8:30 am after what appears to be only 6000 queries or so. Does this mean we stop using the Google API? I don’t know. I will update this post today as we take a look at what happened. What actually happened was the wrong Google API key was in there and it did run out of queries. It is fixed now and I feel silly. I need to keep an eye on the queries though, there are an awful lot in a 24 hour period. Also, there are problems with the keyword search and how it all functions. That will be fixed.
In the meantime, the old search is back Cache is cleared and things are back to using the new search. This is version 2.0 but 2.1 is not far behind. With 2.1 the search will:
- not query Google if UWdir results are returned, why? Because you have to be pretty accurate to get UWdir results so you are likely looking for a person.
- Keyword queries need to be more forgiving because very few ‘titles’ in the db have keywords associated with them. 800 or so entries over 8 years, tough to keep on top of. Just working on cleaning that up. That is why the old one is long dead.
- better tracking of search terms and results
Oh and the stuff listed in the other post…
