Search (3 results, page 1 of 1)

0.004977905 = product of:
  0.014933716 = sum of:
    0.014933716 = product of:
      0.029867431 = sum of:
        0.029867431 = weight(_text_:web in 1213) [ClassicSimilarity], result of:
          0.029867431 = score(doc=1213,freq=2.0), product of:
            0.1656677 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.050763648 = queryNorm
            0.18028519 = fieldWeight in 1213, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1213)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Google Scholar has been well received by the research community. Its promises of free, universal, and easy access to scientific literature coupled with the perception that it covers the social sciences and the humanities better than other traditional multidisciplinary databases have contributed to the quick expansion of Google Scholar Citations and Google Scholar Metrics: 2 new bibliometric products that offer citation data at the individual level and at journal level. In this article, we show the results of an experiment undertaken to analyze Google Scholar's capacity to detect citation-counting manipulation. For this, we uploaded 6 documents to an institutional web domain that were authored by a fictitious researcher and referenced all the publications of the members of the EC3 research group at the University of Granada. The detection by Google Scholar of these papers caused an outburst in the number of citations included in the Google Scholar Citations profiles of the authors. We discuss the effects of such an outburst and how it could affect the future development of such products, at both the individual level and the journal level, especially if Google Scholar persists with its lack of transparency.

0.004977905 = product of:
  0.014933716 = sum of:
    0.014933716 = product of:
      0.029867431 = sum of:
        0.029867431 = weight(_text_:web in 3225) [ClassicSimilarity], result of:
          0.029867431 = score(doc=3225,freq=2.0), product of:
            0.1656677 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.050763648 = queryNorm
            0.18028519 = fieldWeight in 3225, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3225)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

We present an analysis of data citation practices based on the Data Citation Index (DCI) (Thomson Reuters). This database launched in 2012 links data sets and data studies with citations received from the other citation indexes. The DCI harvests citations to research data from papers indexed in the Web of Science. It relies on the information provided by the data repository. The findings of this study show that data citation practices are far from common in most research fields. Some differences have been reported on the way researchers cite data: Although in the areas of science and engineering & technology data sets were the most cited, in the social sciences and arts & humanities data studies play a greater role. A total of 88.1% of the records have received no citation, but some repositories show very low uncitedness rates. Although data citation practices are rare in most fields, they have expanded in disciplines such as crystallography and genomics. We conclude by emphasizing the role that the DCI could play in encouraging the consistent, standardized citation of research data-a role that would enhance their value as a means of following the research process from data collection to publication.

0.0045851828 = product of:
  0.013755548 = sum of:
    0.013755548 = product of:
      0.027511096 = sum of:
        0.027511096 = weight(_text_:22 in 4633) [ClassicSimilarity], result of:
          0.027511096 = score(doc=4633,freq=2.0), product of:
            0.17776565 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050763648 = queryNorm
            0.15476047 = fieldWeight in 4633, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=4633)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

20. 1.2015 18:30:22