Search (5 results, page 1 of 1)

0.016059995 = product of:
  0.03211999 = sum of:
    0.03211999 = sum of:
      0.0071598003 = weight(_text_:a in 4633) [ClassicSimilarity], result of:
        0.0071598003 = score(doc=4633,freq=14.0), product of:
          0.053105544 = queryWeight, product of:
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.046056706 = queryNorm
          0.13482209 = fieldWeight in 4633, product of:
            3.7416575 = tf(freq=14.0), with freq of:
              14.0 = termFreq=14.0
            1.153047 = idf(docFreq=37942, maxDocs=44218)
            0.03125 = fieldNorm(doc=4633)
      0.02496019 = weight(_text_:22 in 4633) [ClassicSimilarity], result of:
        0.02496019 = score(doc=4633,freq=2.0), product of:
          0.16128273 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046056706 = 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)

Abstract

Purpose The purpose of this paper is to analyze the capabilities, functionalities and appropriateness of Altmetric.com as a data source for the bibliometric analysis of books in comparison to PlumX. Design/methodology/approach The authors perform an exploratory analysis on the metrics the Altmetric Explorer for Institutions, platform offers for books. The authors use two distinct data sets of books. On the one hand, the authors analyze the Book Collection included in Altmetric.com. On the other hand, the authors use Clarivate's Master Book List, to analyze Altmetric.com's capabilities to download and merge data with external databases. Finally, the authors compare the findings with those obtained in a previous study performed in PlumX. Findings Altmetric.com combines and orderly tracks a set of data sources combined by DOI identifiers to retrieve metadata from books, being Google Books its main provider. It also retrieves information from commercial publishers and from some Open Access initiatives, including those led by university libraries, such as Harvard Library. We find issues with linkages between records and mentions or ISBN discrepancies. Furthermore, the authors find that automatic bots affect greatly Wikipedia mentions to books. The comparison with PlumX suggests that none of these tools provide a complete picture of the social attention generated by books and are rather complementary than comparable tools. Practical implications This study targets different audience which can benefit from the findings. First, bibliometricians and researchers who seek for alternative sources to develop bibliometric analyses of books, with a special focus on the Social Sciences and Humanities fields. Second, librarians and research managers who are the main clients to which these tools are directed. Third, Altmetric.com itself as well as other altmetric providers who might get a better understanding of the limitations users encounter and improve this promising tool. Originality/value This is the first study to analyze Altmetric.com's functionalities and capabilities for providing metric data for books and to compare results from this platform, with those obtained via PlumX.

Date

20. 1.2015 18:30:22

Type

a

0.001913537 = product of:
  0.003827074 = sum of:
    0.003827074 = product of:
      0.007654148 = sum of:
        0.007654148 = weight(_text_:a in 4141) [ClassicSimilarity], result of:
          0.007654148 = score(doc=4141,freq=16.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.14413087 = fieldWeight in 4141, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.03125 = fieldNorm(doc=4141)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Following the transition from print journals to electronic (hybrid) journals in the past decade, usage metrics have become an interesting complement to citation metrics. In this article we investigate the similarities of and differences between usage and citation indicators for pharmacy and pharmacology journals and relate the results to a previous study on oncology journals. For the comparison at journal level we use the classical citation indicators as defined in the Journal Citation Reports and compute the corresponding usage indicators. At the article level we not only relate download and citation counts to each other but also try to identify the possible effect of citations upon subsequent downloads. Usage data were provided by ScienceDirect both at the journal level and, for a few selected journals, on a paper-by-paper basis. The corresponding citation data were retrieved from the Web of Science and Journal Citation Reports. Our analyses show that electronic journals have become generally accepted over the last decade. While the supply of ScienceDirect pharma journals rose by 50% between 2001 and 2006, the total number of article downloads (full-text articles [FTAs]) multiplied more than 5-fold in the same period. This also impacted the pattern of scholarly communication (strong increase in the immediacy index) in the past few years. Our results further reveal a close relation between citation and download frequencies. We computed a high correlation at the journal level when using absolute values and a moderate to high correlation when relating usage and citation impact factors. At the article level the rank correlation between downloads and citations was only medium-sized. Differences between downloads and citations exist in terms of obsolescence characteristics. While more than half of the articles are downloaded in the publication year or 1 year later, the median cited half-life was nearly 6 years for our journal sample. Our attempt to reveal a direct influence of citations upon downloads proved not to be feasible.

Type

a

0.0014351527 = product of:
  0.0028703054 = sum of:
    0.0028703054 = product of:
      0.005740611 = sum of:
        0.005740611 = weight(_text_:a in 5958) [ClassicSimilarity], result of:
          0.005740611 = score(doc=5958,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.10809815 = fieldWeight in 5958, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=5958)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Location

A

Type

a

0.0011839407 = product of:
  0.0023678814 = sum of:
    0.0023678814 = product of:
      0.0047357627 = sum of:
        0.0047357627 = weight(_text_:a in 154) [ClassicSimilarity], result of:
          0.0047357627 = score(doc=154,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.089176424 = fieldWeight in 154, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=154)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0010148063 = product of:
  0.0020296127 = sum of:
    0.0020296127 = product of:
      0.0040592253 = sum of:
        0.0040592253 = weight(_text_:a in 718) [ClassicSimilarity], result of:
          0.0040592253 = score(doc=718,freq=2.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.07643694 = fieldWeight in 718, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=718)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a