Search (5 results, page 1 of 1)

0.023291955 = product of:
  0.04658391 = sum of:
    0.04658391 = product of:
      0.09316782 = sum of:
        0.09316782 = weight(_text_:light in 35) [ClassicSimilarity], result of:
          0.09316782 = score(doc=35,freq=2.0), product of:
            0.2920221 = queryWeight, product of:
              5.7753086 = idf(docFreq=372, maxDocs=44218)
              0.050563898 = queryNorm
            0.31904373 = fieldWeight in 35, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.7753086 = idf(docFreq=372, maxDocs=44218)
              0.0390625 = fieldNorm(doc=35)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This study investigated the stability of Twitter counts of scientific publications over time. For this, we conducted an analysis of the availability statuses of over 2.6 million Twitter mentions received by the 1,154 most tweeted scientific publications recorded by Altmetric.com up to October 2017. The results show that of the Twitter mentions for these highly tweeted publications, about 14.3% had become unavailable by April 2019. Deletion of tweets by users is the main reason for unavailability, followed by suspension and protection of Twitter user accounts. This study proposes two measures for describing the Twitter dissemination structures of publications: Degree of Originality (i.e., the proportion of original tweets received by an article) and Degree of Concentration (i.e., the degree to which retweets concentrate on a single original tweet). Twitter metrics of publications with relatively low Degree of Originality and relatively high Degree of Concentration were observed to be at greater risk of becoming unstable due to the potential disappearance of their Twitter mentions. In light of these results, we emphasize the importance of paying attention to the potential risk of unstable Twitter counts, and the significance of identifying the different Twitter dissemination structures when studying the Twitter metrics of scientific publications.

0.023291955 = product of:
  0.04658391 = sum of:
    0.04658391 = product of:
      0.09316782 = sum of:
        0.09316782 = weight(_text_:light in 265) [ClassicSimilarity], result of:
          0.09316782 = score(doc=265,freq=2.0), product of:
            0.2920221 = queryWeight, product of:
              5.7753086 = idf(docFreq=372, maxDocs=44218)
              0.050563898 = queryNorm
            0.31904373 = fieldWeight in 265, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.7753086 = idf(docFreq=372, maxDocs=44218)
              0.0390625 = fieldNorm(doc=265)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

To provide some context for the potential engagement behavior of Twitter users around science, this article investigates how Bitly short links to scientific publications embedded in scholarly Twitter mentions are clicked on Twitter. Based on the click metrics of over 1.1 million Bitly short links referring to Web of Science (WoS) publications, our results show that around 49.5% of them were not clicked by Twitter users. For those Bitly short links with clicks from Twitter, the majority of their Twitter clicks accumulated within a short period of time after they were first tweeted. Bitly short links to the publications in the field of Social Sciences and Humanities tend to attract more clicks from Twitter over other subject fields. This article also assesses the extent to which Twitter clicks are correlated with some other impact indicators. Twitter clicks are weakly correlated with scholarly impact indicators (WoS citations and Mendeley readers), but moderately correlated to other Twitter engagement indicators (total retweets and total likes). In light of these results, we highlight the importance of paying more attention to the click metrics of URLs in scholarly Twitter mentions, to improve our understanding about the more effective dissemination and reception of science information on Twitter.

0.008563388 = product of:
  0.017126776 = sum of:
    0.017126776 = product of:
      0.034253553 = sum of:
        0.034253553 = weight(_text_:22 in 2759) [ClassicSimilarity], result of:
          0.034253553 = score(doc=2759,freq=2.0), product of:
            0.17706616 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050563898 = queryNorm
            0.19345059 = fieldWeight in 2759, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2759)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 3.2009 19:02:48

0.008563388 = product of:
  0.017126776 = sum of:
    0.017126776 = product of:
      0.034253553 = sum of:
        0.034253553 = weight(_text_:22 in 2598) [ClassicSimilarity], result of:
          0.034253553 = score(doc=2598,freq=2.0), product of:
            0.17706616 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050563898 = queryNorm
            0.19345059 = fieldWeight in 2598, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2598)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

20. 1.2015 18:30:22

0.0068507106 = product of:
  0.013701421 = sum of:
    0.013701421 = product of:
      0.027402842 = sum of:
        0.027402842 = weight(_text_:22 in 4051) [ClassicSimilarity], result of:
          0.027402842 = score(doc=4051,freq=2.0), product of:
            0.17706616 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050563898 = queryNorm
            0.15476047 = fieldWeight in 4051, 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=4051)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

20. 1.2015 18:30:22