A very large part of my work involves searching. I enter queries into library catalogs, into dictionaries, into search engines, and into academic databases. Anything I can do to reduce the number of steps it takes to perform a search will save me lots of time in the long run. So here is a way to set up custom search engines in your browser. For example, suppose I want to search for a word in JSTOR. In my browser I could
- click my JSTOR bookmark,
- click the search box,
- type my query and hit enter.
But using this hack, I can reduce that process by one step, so that I
- go to search box (in Google Chrome, CMD + L gets you there fast) and
- type ‘JSTOR’ plus tab plus my query and hit enter.
To make this work, you have to know a little bit about how URLs work. URLs can hold all sorts of useful (and hackable) information. For example, suppose I go to JSTOR and search for the word “colporteur” (since it comes up a lot in my sources). The resulting URL is complicated:
That’s hard to read. But I do know that I searched for the word “colporteur,” and sure enough, that word shows up in the URL. The relevant part is
?q0=colporteur. I can deduce that if I replaced that word with another search term (say, “American Tract Society”) and kept everything else the same, I would get a JSTOR query on that term. That is indeed what happens.*
Armed with that information, I can now create my custom search engine. I’ll explain how to do this in Google Chrome (manufacturer’s instructions here), though you can do something similar in Mozilla Firefox, which Brian wrote about two years ago, in Alfred, and doubtless in other applications.
In the first two boxes, we can add the basic information. Let’s call this search engine “JSTOR” (first box) and use the keyword
jstor (second box) to signal Chrome when we want to use this search engine. Then in the third box, we can tell Chrome what a typical search URL looks like for the JSTOR website. Into that box we can paste the long JSTOR URL from above. But where the word “colporteur” appeared, we’re going to substitute the characters
%s. Whenever you use this search engine, Chrome will put the query that you type there.
I have custom search engines set up for LouFind (my library catalog), the Library of Congress, WorldCat, Google Books, BookFinder, Google Scholar, ProfHacker, the Oxford English Dictionary, and a number of subject-specific databases. Setting up a custom search engine like this is worth the trouble for any database or site you’ll search more than twice. You’ll only save 2 to 5 seconds each query, but multiplying that times thousands of searches (not to mention avoiding unnecessary drag on your work) gives you a big savings.
What custom search engines do you use? Do you have any favorite URL hacks?
* If you want a fuller explanation, read about query strings. Bonus tip: the
.resources.library.brandeis.edu part of the URL sends me to JSTOR through my university’s proxy, so I actually get access to JSTOR. Your institution probably has something similar set up.