<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D0YDQ3w9eyp7ImA9WhRVFEQ.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027</id><updated>2012-01-13T14:52:52.263-08:00</updated><title>Google Scholar Blog</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://googlescholar.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://googlescholar.blogspot.com/" /><author><name>Jordan N.</name><uri>http://www.blogger.com/profile/16901237984070230091</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>11</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/GoogleScholarBlog" /><feedburner:info uri="googlescholarblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;DkUHQno8eSp7ImA9WhRSFUw.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-7562586217073945447</id><published>2011-11-16T20:30:00.000-08:00</published><updated>2011-11-16T23:17:13.471-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-11-16T23:17:13.471-08:00</app:edited><title>Google Scholar Citations Open To All</title><content type="html">A few months ago, we introduced &lt;a href="http://googlescholar.blogspot.com/2011/07/google-scholar-citations.html"&gt;a limited release of Google Scholar Citations&lt;/a&gt;, a simple way for authors to compute their citation metrics and track them over time. Today, we’re delighted to make this service available to everyone! &lt;a href="http://scholar.google.com/citations?view_op=new_profile&amp;hl=en"&gt;Click here and follow the instructions to get started&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Here’s how it works. You can quickly identify which articles are yours, by selecting one or more groups of articles that are computed statistically. Then, we collect citations to your articles, graph them over time, and compute your citation metrics - the widely used h-index; the i-10 index, which is simply the number of articles with at least ten citations; and, of course, the total number of citations to your articles. Each metric is computed over all citations and also over citations in articles published in the last five years.&lt;br /&gt;&lt;br /&gt;Your citation metrics will update automatically as we find new citations to your articles on the web. You can also set up automated updates for the list of your articles, or you can choose to review the suggested updates. And you can, of course, manually update your profile by adding missing articles, fixing bibliographic errors, and merging duplicate entries.&lt;br /&gt;&lt;br /&gt;As one would expect, you can search for profiles of colleagues, co-authors, or other researchers using their name, affiliation, or areas of interest, e.g., &lt;a href="http://scholar.google.com/citations?hl=en&amp;view_op=search_authors&amp;mauthors=edu"&gt;researchers at US universities&lt;/a&gt; or &lt;a href="http://scholar.google.com/citations?view_op=search_authors&amp;hl=en&amp;mauthors=label:genomics"&gt;researchers interested in genomics&lt;/a&gt;. You can add links to your co-authors, if they already have a profile, or you can invite them to create one.&lt;br /&gt;&lt;br /&gt;You can also make your profile public, e.g., &lt;a href="http://scholar.google.com/citations?user=kStFxtkAAAAJ&amp;hl=en"&gt;Alex Verstak&lt;/a&gt;, &lt;a href="http://scholar.google.com/citations?user=nGEWZbkAAAAJ&amp;hl=en"&gt;Anurag Acharya&lt;/a&gt;. If you choose to make your profile public, it can appear in Google Scholar search results when someone searches for your name, e.g., &lt;a href="http://scholar.google.com/scholar?hl=en&amp;q=alex+verstak&amp;btnG=Search&amp;as_sdt=0%2C5&amp;as_ylo=&amp;as_vis=0"&gt;[alex verstak]&lt;/a&gt;. This will make it easier for your colleagues worldwide to follow your work.&lt;br /&gt;&lt;br /&gt;We would like to thank the participants in the limited release of Scholar Citations for their detailed feedback. They were generous with their time and patient with an early version. Their feedback greatly helped us improve the service. The key challenge was to make profile maintenance as hands-free as possible for those of you who prefer the convenience of automated updates, while providing as much flexibility as possible for those who prefer to curate their profile themselves.&lt;br /&gt;&lt;br /&gt;Here is hoping that Google Scholar Citations will help researchers everywhere view and track the worldwide influence of their own and their colleagues’ work.&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by: James Connor, Software Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-7562586217073945447?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/LFxinIutvys" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/7562586217073945447?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/7562586217073945447?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/LFxinIutvys/google-scholar-citations-open-to-all.html" title="Google Scholar Citations Open To All" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/11/google-scholar-citations-open-to-all.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0ACSXs6fSp7ImA9WhdQFE4.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-476605807579505152</id><published>2011-08-15T10:53:00.000-07:00</published><updated>2011-08-15T12:16:08.515-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-15T12:16:08.515-07:00</app:edited><title>Shall I compare thee to... a cytotoxicity assay?</title><content type="html">You don't have to be an English lit major to appreciate Shakespeare's endless store of witticisms, catch-phrases and quotes. Which is why it makes us chuckle a bit when we encounter scholarly research articles that reference them in unexpected ways:
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;To sleep, perchance to dream (Hamlet)&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://psycnet.apa.org/psycinfo/1999-11035-007"&gt;Nocturnal eating syndromes: to sleep, perchance to eat&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://www.ersj.org.uk/content/14/6/1241.full.pdf"&gt;To sleep, perchance to leak&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;q=intitle%3Ato-*-perchance-to&amp;btnG=Search&amp;as_sdt=0%2C5&amp;as_ylo=&amp;as_vis=0"&gt;More...&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;To be, or not to be, that is the question (Hamlet)&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://www.jstor.org/pss/2233864"&gt;To slow or not to slow: the economics of the greenhouse effect&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://onlinelibrary.wiley.com/doi/10.1002/etc.5620140509/abstract"&gt;To normalize or not to normalize? Fat is the question&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;q=intitle%3Ato-*-or-not-to&amp;btnG=Search&amp;as_sdt=0%2C5&amp;as_ylo=&amp;as_vis=0"&gt;More... &lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;Much Ado About Nothing&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://books.google.com/books?hl=en&amp;amp;lr=&amp;amp;id=WXGIzbSSddIC&amp;amp;oi=fnd&amp;amp;pg=PA12&amp;amp;ots=LYMVVp08Dg#v=onepage&amp;amp;q&amp;amp;f=false"&gt;The placebo: Is it much ado about nothing&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://www.pnas.org/content/96/25/14177.short"&gt;Programmed ribosomal frameshifting: Much ado about knotting!&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;amp;q=intitle:%22much+ado+about%22&amp;amp;btnG=Search&amp;amp;as_sdt=0%2C5&amp;amp;as_ylo=&amp;amp;as_vis=0"&gt;More...&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;Romeo, Romeo, wherefore art thou, Romeo (Romeo and Juliet)&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://portal.acm.org/citation.cfm?id=1242598"&gt;Wherefore art thou r3579x?: anonymized social networks, hidden patterns, and structural steganography&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://onlinelibrary.wiley.com/doi/10.1002/1521-3773(20001103)39:21%3C3750::AID-ANIE3750%3E3.0.CO;2-L/abstract"&gt;Wherefore Art Thou Copper? Structures and Reaction Mechanisms of Organocuprate Clusters in Organic Chemistry&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;amp;q=intitle%3A%22wherefore+art+thou%22&amp;amp;btnG=Search&amp;amp;as_sdt=0%2C5&amp;amp;as_ylo=&amp;amp;as_vis=0"&gt;More...&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;Et tu, Brute? (Julius Caesar)&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://heinonline.org/HOL/LandingPage?collection=journals&amp;amp;handle=hein.journals/davlr38&amp;amp;div=18&amp;amp;id=&amp;amp;page="&gt;Et Tu, Fair Use-The Triumph of Natural-Law Copyright&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://onlinelibrary.wiley.com/doi/10.1002/art.10609/abstract"&gt;Et tu, acetaminophen?&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;amp;q=intitle:%22et+tu%22&amp;amp;btnG=Search&amp;amp;as_sdt=0%252C5&amp;amp;as_ylo=&amp;amp;as_vis=0"&gt;More...&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;b&gt;All that glisters is not gold (The Merchant of Venice)&lt;/b&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://www.sciencedirect.com/science/article/pii/S0264410X07012236"&gt;All that palsies is not Bell's—The need to define Bell's palsy as an adverse event following immunization&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://onlinelibrary.wiley.com/doi/10.1046/j.1365-2044.1998.00577.x/abstract"&gt;All that wheezes is not asthma&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?hl=en&amp;q=intitle%3A%22all+that+*+is+not%22&amp;btnG=Search&amp;as_sdt=0%2C5&amp;as_ylo=&amp;as_vis=0"&gt;More...&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;There are many more. Happy hunting!
&lt;br /&gt;
&lt;br /&gt;&lt;font color="gray"&gt;Posted by: Darcy Dapra, Partner Manager&lt;/font&gt;
&lt;br /&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-476605807579505152?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/yUyTgUlD8LA" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/476605807579505152?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/476605807579505152?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/yUyTgUlD8LA/shall-i-compare-thee-to-cytotoxicity.html" title="Shall I compare thee to... a cytotoxicity assay?" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/08/shall-i-compare-thee-to-cytotoxicity.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DE8GQXg8eSp7ImA9WhdRFEU.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-5785154511545936637</id><published>2011-08-04T12:25:00.000-07:00</published><updated>2011-08-04T12:40:20.671-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-04T12:40:20.671-07:00</app:edited><title>Google Scholar usage by browser</title><content type="html">&lt;p&gt;As webmasters dabble into the land of exciting possibilities enabled by recent developments in browser technology, it's essential to remember that different users use different browsers, and webpages that work in one browser will not necessarily work in another. But developer time is limited - so, how important is it for a scholarly website to support version N of browser B? To help answer this qestion, here's the breakdown of Google Scholar searches by browser, fresh from the logs.&lt;/p&gt;&lt;table style="border-width:2px;border-style:outset;background-color:#eeeeee" width="100%" cellspacing="0" cellpadding="0"&gt;&lt;caption&gt;&lt;i&gt;Fraction of Google Scholar searches by browser for periods ending August 2, 2011.&lt;/i&gt;&lt;/caption&gt;&lt;tbody&gt;&lt;tr bgcolor="#88cc88"&gt;&lt;th&gt; &lt;/th&gt;&lt;th&gt;year&lt;/th&gt;&lt;th&gt;month&lt;/th&gt;&lt;th&gt;day&lt;/th&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;Internet Explorer&lt;/th&gt;&lt;td align="right"&gt;59%&lt;/td&gt;&lt;td align="right"&gt;47%&lt;/td&gt;&lt;td align="right"&gt;46%&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;Firefox&lt;/th&gt;&lt;td align="right"&gt;25%&lt;/td&gt;&lt;td align="right"&gt;23%&lt;/td&gt;&lt;td align="right"&gt;23%&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;Chrome &amp;amp; Safari&lt;/th&gt;&lt;td align="right"&gt;10%&lt;/td&gt;&lt;td align="right"&gt;19%&lt;/td&gt;&lt;td align="right"&gt;20%&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;Unknown&lt;/th&gt;&lt;td align="right"&gt;5%&lt;/td&gt;&lt;td align="right"&gt;10%&lt;/td&gt;&lt;td align="right"&gt;10%&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;th&gt;Other&lt;/th&gt;&lt;td align="right"&gt;1%&lt;/td&gt;&lt;td align="right"&gt;1%&lt;/td&gt;&lt;td align="right"&gt;1%&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;And now for the fine print...&lt;/p&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;This table doesn't necessarily represent trends in browser adoption, because Google Scholar usage is qualitatively different throughout the year.  In particular, summer numbers do not include frantic searches by thundering herds of students studying for their exams; but annual numbers do.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;These numbers are certainly heavily influenced by English searches.  However, over half of our usage is from outside the US, and non-English speakers tend to search in their own language.  Yes, for papers too; yes, I checked; and yes, some of their searches are in English.  All things considered, I think the world stats should work well for most websites.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;As of last month, versions 7, 8 and 9 of Internet Explorer were used in 18%, 21% and 3% of all searches, respectively.  Versions 5 and 6 carry some, uhh, surprises for developers, but luckily their usage has dropped from 3% + 15% = 18% in the annual stats to 0% + 5% = 5% in the monthly stats.  So, that settles it - we will only test Google Scholar with IE7+ going forward.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Firefox-wise, 10% of total usage is from version 3, and the vast majority of the remaining 13% is from versions 4 and 5.  All three versions are quite similar in their rendering of HTML, so it's often sufficient to cover just the latest version in testing.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;I have combined the two Webkit-based browsers, Chrome and Safari, because their rendering of HTML is nearly identical.  For minor changes, we often test the latest version of Chrome and skip Safari, because Chrome's usage is currently 15% vs. Safari's 5%.  Both of these browsers tend to be reasonably up to date - the vast majority of their searches last month came from Chrome versions 12 and 13 and Safari version 5.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;All mobile browsers combined currently make up a very small fraction of searches, though whether one can call millions of searches "very small" is certainly a matter of perspective.  The same applies to Opera and to a number of other browsers and platforms.  Occasional testing of infrequently used browsers is key to a reasonable balance between serving your users and taking forever to rollout.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;Bottom line?  We recommend that you test your scholarly website with at least three browsers - &lt;b&gt;Internet Explorer 7+&lt;/b&gt;, &lt;b&gt;Firefox 3+&lt;/b&gt;, and &lt;b&gt;Chrome 12+&lt;/b&gt;.  If it doesn't work with either one of these browsers, then it likely doesn't work for a lot of your users.&lt;/p&gt;&lt;p&gt;&lt;font color="gray"&gt;Posted by: Alex Verstak, Software Engineer&lt;/font&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-5785154511545936637?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/C8XLTtu3gh4" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/5785154511545936637?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/5785154511545936637?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/C8XLTtu3gh4/google-scholar-usage-by-browser.html" title="Google Scholar usage by browser" /><author><name>Alex Verstak</name><uri>http://www.blogger.com/profile/05423565547247889489</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/08/google-scholar-usage-by-browser.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYERHk6eSp7ImA9WhdRFE8.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-6529168007569051835</id><published>2011-07-20T15:41:00.000-07:00</published><updated>2011-08-03T18:41:45.711-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-08-03T18:41:45.711-07:00</app:edited><title>Google Scholar Citations</title><content type="html">Citation metrics are often used to gauge the influence of scholarly articles and authors.  Some of you already track your citation metrics by regularly looking up your articles in Google Scholar.  Many of you have asked us for an easier way to do this.&lt;br /&gt;&lt;br /&gt;Today we’re introducing Google Scholar Citations: a simple way for you to compute your citation metrics and track them over time.&lt;br /&gt;&lt;br /&gt;We use a statistical model based on author names, bibliographic data, and article content to group articles likely written by the same author.  You can quickly identify your articles using these groups.  After you identify your articles, we collect citations to them, graph these citations over time, and compute your citation metrics.  Three metrics are available: the widely used &lt;em&gt;h-index&lt;/em&gt;, the &lt;em&gt;i-10 index&lt;/em&gt;, which is the number of articles with at least ten citations, and the total number of citations to your articles.  We compute each metric over all citations as well as over citations in articles published in the last five years.  These metrics are automatically updated as we find new citations to your articles on the web.&lt;br /&gt;&lt;br /&gt;You can enable automatic addition of your newly published articles to your profile.  This would instruct the Google Scholar indexing system  to update your profile as it discovers new articles that are likely yours.  And you can, of course, manually update your profile by adding missing articles, fixing bibliographic errors, and merging duplicate entries.&lt;br /&gt;&lt;br /&gt;You can also create a public profile with your articles and citation metrics (e.g., &lt;a href="http://scholar.google.com/citations?user=kStFxtkAAAAJ&amp;hl=en"&gt;Alex Verstak&lt;/a&gt;, &lt;a href="http://scholar.google.com/citations?user=nGEWZbkAAAAJ&amp;hl=en"&gt;Anurag Acharya&lt;/a&gt;).  If you make your profile public, it can appear in Google Scholar search results when someone searches for your name (e.g., &lt;a href="http://scholar.google.com/scholar?q=richard+feynman"&gt;Richard Feynman&lt;/a&gt;, &lt;a href="http://scholar.google.com/scholar?q=paul+dirac"&gt;Paul Dirac&lt;/a&gt;).  This will make it easier for your colleagues worldwide to follow your work.&lt;br /&gt;&lt;br /&gt;Google Scholar Citations is currently in limited launch with a small number of users. This is a new direction for us and we plan to use the experience and feedback from the limited launch to improve the service. Click &lt;a href="http://scholar.google.com/citations?view_op=new_profile"&gt;here&lt;/a&gt; and follow the instructions to get started. Keep in mind that this is a limited launch and we may not be able to accept new users when you click. If this happens, we’ll direct you to a sign-up page where you can register to be notified when Google Scholar Citations is available to all users. Meanwhile you can browse existing profiles (e.g., &lt;a href="http://scholar.google.com/citations?user=qc6CJjYAAAAJ&amp;hl=en"&gt;Albert Einstein&lt;/a&gt;, &lt;a href="http://scholar.google.com/citations?user=BuIHPK4AAAAJ&amp;hl=en"&gt;Margaret Mead&lt;/a&gt;, &lt;a href="http://scholar.google.com/citations?user=5NUaEngAAAAJ&amp;hl=en"&gt;Alonzo Church&lt;/a&gt;) and &lt;a href="http://scholar.google.com/intl/en/scholar/citations.html"&gt;learn more about Google Scholar Citations&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Update:&lt;/b&gt; We are not able to accept new users at this point. We invite you to &lt;a href="http://scholar.google.com/citations?view_op=email_signup_options&amp;hl=en"&gt;sign up&lt;/a&gt; to be notified when Google Scholar Citations is available to all users. &lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by: James Connor, Software Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-6529168007569051835?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/MoDXY5z5Fco" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/6529168007569051835?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/6529168007569051835?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/MoDXY5z5Fco/google-scholar-citations.html" title="Google Scholar Citations" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/07/google-scholar-citations.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkUHSXszeyp7ImA9WhdTEEw.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-4874647870793383520</id><published>2011-07-06T21:38:00.000-07:00</published><updated>2011-07-06T21:50:38.583-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-07-06T21:50:38.583-07:00</app:edited><title>Work Locally, Search Globally</title><content type="html">Recently, I spent a month in Ghana working with NGOs and some government organizations. As a part of this, I visited a health research center in Dodowa, couple of hours from Accra. Staff members gather disease and demographics data from the district for research as well as for health policy recommendations.&lt;br /&gt;&lt;br /&gt;The center is in the middle of farmlands with no access to landline phones - Internet access is via flaky mobile networks.  When I introduced myself as an engineer working on Google Scholar, I expected I would need to describe Scholar at length and do some demos. I was, however, pleasantly surprised to see eyes light up with recognition. So, I talked to the staff members trying to understand how they use Scholar.&lt;br /&gt;&lt;br /&gt;The research center maintains a digital library of scholarly articles related to malaria which is the biggest disease threat in the region.  This library is used by researchers at the center as well as by a larger network of scientists interested in malaria.  Alexander Nartey (program coordinator) curates the library and uses Scholar to discover newly published papers.  Doris Sarpong (demographer/research officer) mentioned that the speed of Scholar helps her get her work done in spite of the limited connectivity. She also liked the ability to restrict  results to recent papers. Alberta Amu Quartey (graduate student) works on the history of malaria serology. Scholar helped her find papers going as far back as the 1960s, many of them from Ghana and neighboring regions.&lt;br /&gt;&lt;br /&gt;The simplest feedback I heard was from an older researcher who had been working in the field for a while. He liked that he could find anything anyone anywhere had discovered. He said,  "A man who has never worn spectacles doesn't really know what he's missing". It is one thing to sit in a conference room in California and argue about Google Scholar features and algorithms and quite another to stand in an African village health center and hear in person what they make possible. Here is hoping Google Scholar can help more researchers in more places see further.&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by Mohit Rajani, Software Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-4874647870793383520?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/otevydo7sMI" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/4874647870793383520?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/4874647870793383520?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/otevydo7sMI/work-locally-search-globally.html" title="Work Locally, Search Globally" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/07/work-locally-search-globally.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ak8ARXg6eip7ImA9WhZUFE0.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-8781770856750715892</id><published>2011-06-06T17:08:00.001-07:00</published><updated>2011-06-06T18:07:24.612-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-06-06T18:07:24.612-07:00</app:edited><title>A scholarly discovery, just in time for Father’s Day</title><content type="html">Recently, I mentioned to my Dad that I would be rejoining the Google Scholar team. Like many of us, I wanted to explain to him what I work on. I entered his name into Google Scholar to do a quick demo. The first result was a US patent, that he had developed with my uncle, for drilling within a spinal column (whew!). And a bit later was an article from 1968 on &lt;a href="http://www.ncbi.nlm.nih.gov/pubmed/5666698"&gt;Acute Histoplasma Pericarditis&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;I said, "Hey Dad, I didn’t know that you had published a scholarly article!”  He didn’t answer, going noticeably silent--for several moments.  Something about that search result brought tears to his eyes (though he would never admit this) and rendered him speechless.  Well, nearly speechless.  I think he said almost inaudibly, “I’ll be...”&lt;br /&gt;&lt;br /&gt;As it turned out, this was a paper he had written with colleagues and had submitted to the Archives of Internal Medicine 40-odd years ago. He had then moved to Spain as an US Air Force flight surgeon. If the editors or his co-authors had sent him a note of congratulations on its acceptance, it never made its way across the Atlantic. He had long forgotten about it.&lt;br /&gt;&lt;br /&gt;On behalf of the Scholar team, and after all these years, congratulations, Dad!&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by Darcy Dapra, Partner Manager&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-8781770856750715892?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/IXQVcH54aOk" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8781770856750715892?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8781770856750715892?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/IXQVcH54aOk/scholarly-discovery-just-in-time-for.html" title="A scholarly discovery, just in time for Father’s Day" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/06/scholarly-discovery-just-in-time-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0QGQXY8eSp7ImA9Wx9UEk8.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-8016030136746722617</id><published>2011-02-08T19:06:00.000-08:00</published><updated>2011-02-08T19:15:20.871-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-08T19:15:20.871-08:00</app:edited><title>Better highlighting for legal cases</title><content type="html">&lt;div&gt;We used to have &lt;b style="background-color: rgb(255, 153, 153); color: black; "&gt;colorful&lt;/b&gt; &lt;b style="background-color: rgb(153, 0, 153); color: white; "&gt;highlighting&lt;/b&gt; for cases. Some users have told us that this is hard to read. We now highlight legal cases more gently and provide an option to remove highlighting entirely. Happy reading!&lt;/div&gt;&lt;div&gt;&lt;br /&gt;&lt;/div&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_ezZQUl1Eaf0/TVIF7sr_vRI/AAAAAAAAAAU/VeUOg7wQTnc/s1600/remove_highlighting_blog_post6.png"&gt;&lt;img style="cursor:pointer; cursor:hand;width: 400px; height: 123px;" src="http://2.bp.blogspot.com/_ezZQUl1Eaf0/TVIF7sr_vRI/AAAAAAAAAAU/VeUOg7wQTnc/s400/remove_highlighting_blog_post6.png" border="0" alt="" id="BLOGGER_PHOTO_ID_5571522212176837906" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="color:gray"&gt;Posted by James Connor, Software Engineer&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-8016030136746722617?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/qcxj3WYfuLo" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8016030136746722617?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8016030136746722617?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/qcxj3WYfuLo/better-highlighting-for-legal-cases.html" title="Better highlighting for legal cases" /><author><name>jconnor</name><uri>http://www.blogger.com/profile/16929217268179391972</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_ezZQUl1Eaf0/TVIF7sr_vRI/AAAAAAAAAAU/VeUOg7wQTnc/s72-c/remove_highlighting_blog_post6.png" height="72" width="72" /><feedburner:origLink>http://googlescholar.blogspot.com/2011/02/better-highlighting-for-legal-cases.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQGQXk7fSp7ImA9Wx9XF0s.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-7096269772773976729</id><published>2011-01-11T09:30:00.000-08:00</published><updated>2011-01-11T09:52:00.705-08:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-11T09:52:00.705-08:00</app:edited><title>Search opinions from specific courts</title><content type="html">When Itai joined the Google Scholar team recently, he noticed many differences between life in New York City and life in the San Francisco Bay Area. One pleasant difference was a sharp drop in near-death experiences involving taxis. With his background as a lawyer, Itai couldn't help but think that there must be a lot fewer taxi-related lawsuits in his new locale! Now that Google Scholar allows users to limit search to specific courts and jurisdictions, he can confirm it—court opinions mentioning a taxi &lt;a href="http://scholar.google.com/scholar?q=taxi&amp;as_sdt=4,351"&gt;in the Southern District of New York&lt;/a&gt; far outnumber those &lt;a href="http://scholar.google.com/scholar?q=taxi&amp;as_sdt=4,323"&gt;in the Northern District of California.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You can try this out yourself on Google Scholar's &lt;a href="http://scholar.google.com/advanced_scholar_search?as_sdt=2&amp;q=taxi"&gt;advanced search page.&lt;/a&gt; You can select a particular federal jurisdiction or state for your search. For example, try searching for cases involving &lt;a href="http://scholar.google.com/scholar?q=oysters&amp;as_sdt=4,55,192"&gt;oysters in tax courts&lt;/a&gt; or &lt;a href="http://scholar.google.com/scholar?q=health+insurance&amp;as_sdt=4,83,96,109,124,146,159,290,291,292,308,309,312,313,353,354,355,371,372,375,376"&gt;health insurance in Fourth Circuit courts.&lt;/a&gt; You can also pick specific courts by clicking on "Select specific courts" and checking off the ones you want. Then you can search for, say, &lt;a href="http://scholar.google.com/scholar?q=oil+spill&amp;as_sdt=4,19,340,341,342&amp;as_ylo=2010"&gt;recent opinions about oil spills in Louisiana state and federal courts&lt;/a&gt; or &lt;a href="http://scholar.google.com/scholar?q=election+recount&amp;as_sdt=4,2,10,24"&gt;cases about election recounts in Florida, Minnesota and Alaska courts.&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Finding the right precedent is of course the key to legal research. Here's hoping this new feature will help you find the right cases even faster.&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by Chris Hundt and Itai Gurari, Software Engineers&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-7096269772773976729?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/T7AftCv5ojU" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/7096269772773976729?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/7096269772773976729?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/T7AftCv5ojU/search-opinions-from-specific-courts.html" title="Search opinions from specific courts" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2011/01/search-opinions-from-specific-courts.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU4CRnwzfyp7ImA9Wx5TEUs.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-6702947828004824806</id><published>2010-07-26T09:00:00.000-07:00</published><updated>2010-07-26T11:12:47.287-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-26T11:12:47.287-07:00</app:edited><title>Entertaining legal opinions</title><content type="html">Judicial opinions in common law countries, like the United States, clarify and  refine the law of the land. They consider weighty issues, weigh conflicting requirements and carry much weight among all who read them. Here are some opinions for your summer reading. &lt;br /&gt;&lt;br /&gt;&lt;div&gt;&lt;br /&gt;&lt;a href="http://scholar.google.com/scholar?q=Rimes+v.+Curb+Records&amp;amp;as_sdt=2002&amp;amp;btnI=Feeling+Lucky"&gt;Rimes v. Curb Records, Inc., 2001&lt;/a&gt; the opinion is written as a series of songs to be sung to tunes by LeAnn Rimes. It starts: &lt;br /&gt;&lt;pre&gt;LeAnn Rimes&lt;br /&gt;A very rich and famous star&lt;br /&gt;Wasn't so rich in times afar&lt;br /&gt;But what a talent she had!&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=347+F.+3d+1212&amp;btnI=Feeling+Lucky"&gt;Glazner v. Glazner, 2003&lt;/a&gt; illustrates one of the arguments using an imagined dialog between spouses (page 1223). &lt;pre&gt;Jim: Honey, I've been thinking, we ought to move to Alabama.&lt;br /&gt;Liz: But Sweetheart, I thought you liked living in Colorado.&lt;br /&gt;...&lt;br /&gt;Liz: You'll look so good in jailhouse stripes, my Love. When do we move?&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=421+Pa.+70&amp;btnI=Feeling+Lucky"&gt;Commonwealth v. Robin, 1966&lt;/a&gt; the case was about banning "Tropic of Cancer" by Henry Miller. Justice Musmanno, in his dissent (starting at page 73), is particularly colorful. E.g.,: &lt;em&gt;"Cancer" is not a book. It is a cesspool, an open sewer, a pit of putrefaction, a slimy gathering of all that is rotten in the debris of human depravity. And in the center of all this waste and stench, besmearing himself with its foulest defilement, splashes, leaps, cavorts and wallows a bifurcated specimen that responds to the name of Henry Miller.&lt;/em&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=Webster+v.+Blue+Ship+Tea+Room,+Inc&amp;btnI=Feeling+Lucky"&gt;Webster v. Blue Ship Tea Room, Inc., 1964&lt;/a&gt; the opinion includes a page-long discussion of recipes &amp; history of chowder starting with (page 424): &lt;em&gt;Chowder is an ancient dish preexisting even "the appetites of our seamen and fishermen." It was perhaps the common ancestor of the "more refined cream soups, purees, and bisques." &lt;/em&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=Pennsylvania+v+Dunlap&amp;btnI=Feeling+Lucky"&gt;Pennsylvania v. Dunlap, 2008&lt;/a&gt; the opinion starts in the hard-boiled detective style: &lt;em&gt;Officer Sean Devlin, Narcotics Strike Force, was working the morning shift. Undercover surveillance. The neighborhood? Tough as a three-dollar steak. Devlin knew. Five years on the beat, nine months with the Strike Force. He'd made fifteen, twenty drug busts in the neighborhood. &lt;/em&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=333+NW2d+67&amp;btnI=Feeling+Lucky"&gt;Fisher v. Lowe, 1983&lt;/a&gt; the entire opinion is in verse and starts: &lt;br /&gt;&lt;pre&gt;We thought that we would never see&lt;br /&gt;A suit to compensate a tree.&lt;br /&gt;A suit whose claim in tort is prest&lt;br /&gt;Upon a mangled tree's behest;&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=732+A.+2d+1274&amp;btnI=Feeling+Lucky"&gt;Busch v. Busch, 1999&lt;/a&gt; also in verse, it starts with:&lt;br /&gt;&lt;pre&gt;Conrad Busch filed a timely appeal, &lt;br /&gt;trying to avoid a pre-marital deal &lt;br /&gt;which says appellee need not pay him support; &lt;br /&gt;he brings his case, properly, before this Court.&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=604+F.+2d+322&amp;btnI=Feeling+Lucky"&gt;Anderson Greenwood &amp; Co. v. NLRB, 1979&lt;/a&gt; two of the relevant precedents were Wire v. NLRB and Tire v. NLRB, an opportunity to break forth in verse the judges did not miss (page 323). E.g., &lt;br /&gt;&lt;pre&gt;Our decision in Robbins Tire,&lt;br /&gt;Interpreting Congresses' reported desires, &lt;br /&gt;Exposed workers to their bosses' ire.&lt;br /&gt;The High Court, avoiding this sticky quagmire,&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?q=315+F.+3d+1143&amp;btnI=Feeling+Lucky&amp;as_sdt=2002"&gt;US v. Ramirez-Lopez, 2003&lt;/a&gt; Judge Kozinski, in his dissent, illustrates his argument using a good-news/bad-news dialog between the defendant and his attorney (page 1159). E.g., &lt;br /&gt;&lt;pre&gt;Lawyer: Juan, I have good news and bad news.&lt;br /&gt;Ramirez-Lopez: OK, I'm ready. Give me the bad news first.&lt;br /&gt;...&lt;br /&gt;Lawyer: Due process. We're very proud of it.&lt;/pre&gt;&lt;/div&gt;&lt;br /&gt;&lt;div&gt;&lt;a href="http://scholar.google.com/scholar?as_sdt=2002&amp;q=903+F.+2d+659&amp;btnI=Feeling+Lucky"&gt;US v. Syufy Enterprises, 1990&lt;/a&gt; this case was about movie theatres in Las Vegas. Judge Kozinski includes the names of over 200 movies into his opinion. If you are a movie buff, challenge yourself and see how many you can find! You can see them marked out &lt;a href="http://notabug.com/kozinski/syufyrosetta.pdf"&gt;here.&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;There are many more such gems. Now that &lt;a href="http://googleblog.blogspot.com/2009/11/finding-laws-that-govern-us.html"&gt;everyone can read US opinions&lt;/a&gt;, you can find some yourself. Happy hunting!&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by Anurag Acharya, Distinguished Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-6702947828004824806?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/uRQg6oXUF-8" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/6702947828004824806?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/6702947828004824806?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/uRQg6oXUF-8/entertaining-legal-opinions.html" title="Entertaining legal opinions" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2010/07/entertaining-legal-opinions.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0EBRXc9eSp7ImA9WxFbEEk.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-8318158841097445422</id><published>2010-07-01T17:30:00.000-07:00</published><updated>2010-07-01T20:34:14.961-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-01T20:34:14.961-07:00</app:edited><title>Search within citing articles</title><content type="html">Ever wanted to trace an article’s impact?  Take for example Einstein’s famous paper &lt;a href="http://link.aps.org/doi/10.1103/PhysRev.47.777"&gt;Can quantum-mechanical description of physical reality be considered complete?&lt;/a&gt;, which has shaped areas as disparate as physics, computer science, and philosophy.  We can examine the article’s influence by looking at &lt;a href="http://scholar.google.com/scholar?cites=3323516001886693479&amp;as_sdt=2005&amp;sciodt=2000"&gt;citations to it&lt;/a&gt;, but there are thousands of citations and sifting through them is unwieldy.&lt;br /&gt;&lt;br /&gt;Today we’re launching the ability to search within this set.  We can see this article’s impact on &lt;a href="http://scholar.google.com/scholar?q=quantum+computation&amp;cites=3323516001886693479&amp;scipsc=1"&gt;quantum computation&lt;/a&gt;, &lt;a href="http://scholar.google.com/scholar?q=cryptography&amp;cites=3323516001886693479&amp;scipsc=1"&gt;cryptography&lt;/a&gt;, &lt;a href="http://scholar.google.com/scholar?q=entanglement&amp;cites=3323516001886693479&amp;scipsc=1"&gt;entanglement&lt;/a&gt;, or &lt;a href="http://scholar.google.com/scholar?q=teleportation&amp;btnG=Search&amp;cites=3323516001886693479&amp;scipsc=1"&gt;teleportation&lt;/a&gt;.  We can see its continuing influence on multiple fields by looking at &lt;a href=" http://scholar.google.com/scholar?cites=3323516001886693479&amp;scipsc=1&amp;as_sdt=2000&amp;as_ylo=2009"&gt;recent citations to it&lt;/a&gt;.  And we can even discover topics that Einstein probably never thought he would influence, like &lt;a href="http://scholar.google.com/scholar?q=holism&amp;cites=3323516001886693479&amp;scipsc=1"&gt;holism&lt;/a&gt; and &lt;a href="http://scholar.google.com/scholar?q=postmodernism&amp;btnG=Search&amp;cites=3323516001886693479&amp;scipsc=1"&gt;postmodernism&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Try it out yourself by clicking on a "Cited by" link on the search results page:&lt;br /&gt;&lt;br /&gt;&lt;div style="border: 2px solid #9fd9a7; text-align: center;"&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_0pDOa2dcPDk/TC0zNeb6GAI/AAAAAAAAAA8/RhWMJjJQKck/s1600/blog-citing.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand; padding: 0.33em; width: 480px; height: 99px;" src="http://3.bp.blogspot.com/_0pDOa2dcPDk/TC0zNeb6GAI/AAAAAAAAAA8/RhWMJjJQKck/s320/blog-citing.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5489099827435935746" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;and selecting the "Search within articles citing..." checkbox:&lt;br /&gt;&lt;br /&gt;&lt;div style="border: 2px solid #9fd9a7; text-align: center;"&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_0pDOa2dcPDk/TC0zXURcHtI/AAAAAAAAABE/bva-3-f2VbM/s1600/blog-checkbox.jpg"&gt;&lt;img style="cursor:pointer; cursor:hand; padding:0.33em; width: 480px; height: 51px;" src="http://1.bp.blogspot.com/_0pDOa2dcPDk/TC0zXURcHtI/AAAAAAAAABE/bva-3-f2VbM/s320/blog-checkbox.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5489099996506365650" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Thank you to those who contacted us to request this feature and hats off to the &lt;a href="http://lifehacker.com/comment/22764833/"&gt;few&lt;/a&gt; who figured out how to emulate it by tweaking the URL.  We hope this helps you to follow the impact and evolution of ideas.&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by James Connor, Software Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-8318158841097445422?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/Jv3e5L6BA8Y" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8318158841097445422?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/8318158841097445422?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/Jv3e5L6BA8Y/search-within-citing-articles.html" title="Search within citing articles" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/_0pDOa2dcPDk/TC0zNeb6GAI/AAAAAAAAAA8/RhWMJjJQKck/s72-c/blog-citing.jpg" height="72" width="72" /><feedburner:origLink>http://googlescholar.blogspot.com/2010/07/search-within-citing-articles.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUMBQHc_cCp7ImA9WxFVFUs.&quot;"><id>tag:blogger.com,1999:blog-7181812908636873027.post-4700230137359492168</id><published>2010-06-15T10:00:00.000-07:00</published><updated>2010-06-14T19:04:11.948-07:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-14T19:04:11.948-07:00</app:edited><title>Google Scholar Alerts</title><content type="html">Ever since we launched Google Scholar, people have asked us to help them keep up with current research.  Over the years, we’ve made several improvements to help find recently published articles, including &lt;a href="http://googleblog.blogspot.com/2006/04/keeping-up-with-recent-research.html"&gt;the "Recent articles" mode&lt;/a&gt;,  a simple interface to limit search to recent years, and, of course, more frequent index updates. As the next step in this endeavor, we have recently added email alerts. Now you can create alerts for queries of your interest. When new articles that match your alert query are added to Google Scholar, we’ll send you an email update with links to these articles.&lt;br /&gt;&lt;br /&gt;To create an alert for a query, just do a search on Google Scholar as usual (e.g., &lt;a href="http://scholar.google.com/scholar?q=prion+protein"&gt;[prion protein]&lt;/a&gt;) and click on the envelope icon which appears at the top of the search results. This will take you to a page with recent results for your query and alert options (e.g., &lt;a href="http://scholar.google.com/scholar_alerts?view_op=create_alert_options&amp;alert_query=intitle:%22prion+protein%22&amp;alert_params=hl%3Den%26as_sdt%3D2000"&gt;alert options for [prion protein]&lt;/a&gt;). If the query returns results other than ones you were looking for, you can tweak it right there and view updated results. Adding more specific search terms often works, and so does placing full author names and multi-word concepts in quotes (e.g., &lt;a href="http://scholar.google.com/scholar_alerts?view_op=create_alert_options&amp;alert_query=%22quantum+computing%22&amp;alert_params=hl%3Den%26as_sdt%3D2000"&gt;[“quantum computing”]&lt;/a&gt;). Then, click on “Create alert” - and bingo! If you’re logged into Gmail, your alert will be created right away. If you’re not logged in, you’ll need to enter your email address and we’ll send you a verification message with links to confirm or cancel the alert. Any email address will do, you don’t need a Gmail account to receive Google Scholar Alerts. Once you click on the confirmation link, your alert will be created and you’ll start receiving email updates on your query.&lt;br /&gt;&lt;br /&gt;To create an alert for articles citing a particular paper, first, find this paper in Google Scholar, then click on the “Cited by” link below the search result, and, finally, click on the envelope icon that appears at the top of  the list of citing articles. To get updates when any of your papers are cited, it’s often easiest to set up an alert for all mentions of your name in text, e.g., &lt;a href="http://scholar.google.com/scholar_alerts?view_op=create_alert_options&amp;alert_query=%22E+Witten%22&amp;alert_params=hl%3Den%26as_sdt%3D200"&gt;[“E Witten”]&lt;/a&gt; with the quotes. To learn of new publications by your colleagues, try registering alerts for their names with an “author:” operator, such as &lt;a href="http://scholar.google.com/scholar_alerts?view_op=create_alert_options&amp;alert_query=author:%22S+Hawking%22&amp;alert_params=hl%3Den%26as_sdt%3D2000"&gt;[author:”S Hawking”]&lt;/a&gt;. If these alerts return too many results related to other people with the same name, try adding more specific search terms, such as the names of their co-authors, the name of the university they are associated with, or plain old keywords.&lt;br /&gt;&lt;br /&gt;So, what does it take to provide an alerts service for the largest collection of research papers on the planet?  Good question. To implement Google Scholar Alerts, we had to solve several tricky problems. First, we had to figure out how to quickly find newly available scholarly articles over the entire web. They can and do appear on a variety of locations - on publisher web sites, in scholarly repositories, on researchers’ web pages. Second, we had to determine which of the newly available articles were recently written or published. This can be difficult since many publishers and universities provide archival articles (which are not new) whereas early presentations of a work, such as preprints (which are indeed new), often have no dates associated with them. Third, we needed to update the index much more frequently. Updating a search service while it is being used by a large number of users is somewhat like changing tires on a car while it is going sixty miles an hour. We now add new articles to Google Scholar twice a week; we plan to further increase this frequency. Finally, we had to develop a query suggestion mechanism to help users construct effective alert queries. Our goal was to help people bridge the gap between finding key articles in a large collection (as they’re doing when they search Google Scholar) and finding relevant articles in the much smaller collection of recently published articles (as they would be doing with alerts). &lt;br /&gt;&lt;br /&gt;We hope Google Scholar Alerts will help researchers everywhere keep up with the discoveries made by their colleagues worldwide.&lt;br /&gt;&lt;br /&gt;&lt;font color="gray"&gt;Posted by Anurag Acharya, Distinguished Engineer&lt;/font&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7181812908636873027-4700230137359492168?l=googlescholar.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/GoogleScholarBlog/~4/Ua4EW3-vXjg" height="1" width="1"/&gt;</content><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/4700230137359492168?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/7181812908636873027/posts/default/4700230137359492168?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/GoogleScholarBlog/~3/Ua4EW3-vXjg/google-scholar-alerts.html" title="Google Scholar Alerts" /><author><name>Anurag</name><uri>http://www.blogger.com/profile/13875945358496589158</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><feedburner:origLink>http://googlescholar.blogspot.com/2010/06/google-scholar-alerts.html</feedburner:origLink></entry></feed>

