If you have ‘linked’ or on-the-fly Google Custom Search Engines, note that they will have stopped working a week or so ago. As planned and announced, at around the end of May 2017 Google withdrew the ‘linked’ CSE option (self-hosted, and a pain to set up and admin). They also withdrew the ‘cref’ URL-path item, which was what enabled an on-the-fly CSE from any page of Web links (handy, but not that often). It’s a pity to see the latter go, but apparently it’s part of a modernisation of the CSE service.<\/p>\n
JURN’s various ongoing search projects are not affected by the changes, as GRAFT has been ported. But if you’re affected, then you now need to either: i) port your search tool’s URLs into a full free CSE, via Google’s CSE console (easiest way is .tsv files containing 500-URL chunks of your list, must be less than 30Kb per .tsv); or ii) use the free DuckDuckGo CSE functionality<\/a> to get a quick CSE which only runs over a handful of URLs. The current drawback of the DuckDuckGo CSE service is that the Duck may not yet have had a good quack at some of the obscure academic sites you may want in your CSE.<\/p>\n","protected":false},"excerpt":{"rendered":" If you have ‘linked’ or on-the-fly Google Custom Search Engines, note that they will have stopped working a week or …<\/p>\n