ReaderMeter: Crowdsourcing research impact► readermeter.org
AboutReaderMeter is a mashup visualizing author-level and article-level metrics based on the readership of scholarly publications by a large academic population. Readership data is obtained via the Mendeley API°. ReaderMeter was officially launched at Science Online London 2010°. It was the first public Web app built on top of the Mendeley API° and the first proof-of-concept altmetrics° application. All ReaderMeter contents (including machine-readable JSON data) are released under a CC-BY-SA 3.0 license. As of August 2012, it has generated 1.7M+ publicly indexed, CC-licensed reports.
ReaderMeter has been featured in the Wall Street Journal (Tech News)°, the Guardian°, the Times Higher Education°, the Journal of Informetrics°, the Oxford Internet Institute's report on the Future of Web archives°, TechCrunch°, The Next Web°, Programmable Web ("mashup of the day")°, The Library Journal°, KnowledgeSpeak°, Campus Technology°, GigaOM° and Killer Startups°. It was shortlisted in the "top 10+1 applications that could impact science" by the Mendeley-PLoS Binary Battle° (2011).
Readers of this blog are not new to my ramblings on soft peer review, social metrics and post-publication impact measures:
- can we measure the impact of scientific research based on usage data from collaborative annotation systems, social bookmarking services and social media?
- should we expect major discrepancies between citation-based and readership-based impact measures?
- are online reference management systems more robust a data source to measure scholarly readership than traditional usage factors (e.g. downloads, clickthrough rates etc.)?
We now need to think of ways of putting these ideas into practice. Science Online London 2010 earlier this month offered a great chance to test a real-world application of these ideas in front of a tech-friendly audience and this post is meant as its official announcement.
ReaderMeter is a proof-of-concept application showcasing the potential of readership data obtained from reference management tools. Following the announcement of the Mendeley API, I decided to see what could be built on top of the data exposed by Mendeley and the first idea was to write a mashup aggregating author-level readership statistics based on the number of bookmarks scored by each of one's publications. ReaderMeter queries the data provider's API for articles matching a given author string. It parses the response and generates a report with several metrics that attempt to quantify the relative impact of an author's scientific production based on its consumption by a population of readers (in this case the 500K-strong Mendeley user base).
The first figure shows a screenshot of ReaderMeter’s results for social scientist Duncan J Watts, displaying global bookmark statistics, the breakdown of readers by publication as well as two indices (the HR index and the GR index) which I compute using bookmarks as a variable by analogy to the two popular citation-based metrics. Clicking on a reference allows you to drill down to display readership statistics for a given publication, including the scientific discipline, academic status and geographic location of readers of an individual document:
A handy permanent URL is generated to link to ReaderMeter’s author reports (using the scheme: [SURNAME].[FIRSTNAME+INITIALS]), e.g.:
"author": "Duncan J Watts",
Despite being just a proof of concept (it was hacked in a couple of nights!), ReaderMeter attracted a number of early testers who gave a try to its first release. Its goal is not to redefine the concept of research impact as we know it, but to complement this notion with usage data from new sources and help identify aspects of impact that may go unnoticed when we only focus on traditional, citation-based metrics. Before a mature version of ReaderMeter is available for public consumption and for integration with other services, though, several issues will need to be addressed.
1. Author name normalisation
The first issue to be tackled is the fact the same individual author may be mentioned in a bibliographic record under a variety of spelling alternates: Rod Page was among the first to spot and extensively discuss this issue, which will hopefully be addressed in the next major upgrade (unless a provision to fix this problem is directly offered by Mendeley in a future upgrade of their API).
2. Article deduplication
A similar issue affects individual bibliographic entries, as noted by Egon Willighagen among others. Given that publication metadata in reference management services can be extracted by a variety of sources, the uniqueness of a bibliographic record is far from given. As a matter of fact, several instances of the same publication can show up as distinct items, with the result of generating flawed statistics when individual publications and their relative impact need to be considered (as is the case when calculating the H- and G-index). To what extent crowdsourced bibliographic databases (such as those of Mendeley, CiteULike, Zotero, Connotea, and similar distributed reference management tools) can tackle the problem of article duplication as effectively as manually curated bibliographic databases, is an interesting issue that sparked a heated debate (see this post by Duncan Hull and the ensuing discussion).
3. Author disambiguation
A way more challenging problem consists in disambiguating real homonyms. At the moment, ReaderMeter is unable to tell the difference between two authors with an identical name. Considering that surnames like Wang appear to be shared by about 100M people on the planet, the problem of how to disambiguate authors with a common surname is not something that can be easily sorted out by a consumer service such as ReaderMeter. Global initiatives with a broad institutional support such as the ORCID project are trying to fix this problem for good by introducing a unique author identifier system, but precisely because of their scale and ambitious goal they are unlikely to provide a viable solution in the short run.
4. Reader segmentation and selection biases
You may wonder: how genuine is data extracted from Mendeley as an indicator of an author's actual readership? Calculating author impact metrics based on the user population of a specific service will always by definition result in skewed results due to different adoption rates by different scientific communities or demographic segments (e.g. by academic status, language, gender) within the same community. And how about readers who just don't use any reference management tools? Björn Brembs posted some thoughtful considerations on why any such attempt at measuring impact based on the specific user population of a given platform/service is doomed to fail. His proposed solution, however – a universal outlet where all scientific content consumption should happen–sounds not only like an unlikely scenario, but also in many ways an undesirable one. Diversity is one of the key features of the open source ecosystem, for one, and as long as interoperability is achieved (witness the example of the OAI protocol and its multiple software implementation), there is certainly no need for a single service to monopolise the research community's attention for projects such as ReaderMeter to be realistically implemented. The next step on ReaderMeter’s roadmap will be to integrate data from a variety of content providers (such as CiteULike or Bibsonomy) that provide free access to article readership information: although not the ultimate solution to the enormous problem of user segmentation, data integration from multiple sources should hopefully help reduce biases introduced by the population of a specific service.
I will be working in the coming days on an upgrade to address some of the most urgent issues, in the meantime feel free to test ReaderMeter, send me your feedback and feature requests, follow the latest news on the project via Twitter or just help spread the word!