Search (1 results, page 1 of 1)

0.02794741 = product of:
  0.05589482 = sum of:
    0.05589482 = product of:
      0.11178964 = sum of:
        0.11178964 = weight(_text_:i in 94) [ClassicSimilarity], result of:
          0.11178964 = score(doc=94,freq=10.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.65227187 = fieldWeight in 94, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.0546875 = fieldNorm(doc=94)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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