Hughes, T.; Acharya, A.: ¬An interview with Anurag Acharya, Google Scholar lead engineer
0.01
0.010779679 = product of:
0.032339036 = sum of:
0.032339036 = weight(_text_:on in 94) [ClassicSimilarity], result of:
0.032339036 = score(doc=94,freq=6.0), product of:
0.109763056 = queryWeight, product of:
2.199415 = idf(docFreq=13325, maxDocs=44218)
0.04990557 = queryNorm
0.29462588 = fieldWeight in 94, product of:
2.4494898 = tf(freq=6.0), with freq of:
6.0 = termFreq=6.0
2.199415 = idf(docFreq=13325, maxDocs=44218)
0.0546875 = fieldNorm(doc=94)
0.33333334 = coord(1/3)
- Abstract
- When I interned at Google last summer after getting my MSI degree, I worked on projects for the Book Search and Google Scholar teams. I didn't know it at the time, but in completing my research over the course of the summer, I would become the resident expert on how universities were approaching Google Scholar as a research tool and how they were implementing Scholar on their library websites. Now working at an academic library, I seized a recent opportunity to sit down with Anurag Acharya, Google Scholar's founding engineer, to delve a little deeper into how Scholar features are developed and prioritized, what Scholar's scope and aims are, and where the product is headed. -Tracey Hughes, GIS Coordinator, Social Sciences & Humanities Library, University of California San Diego
