ACM Usage Statistics

ACM Counter 4 Compliant Usage Statistics

The ACM provides COUNTER 4 compliant usage statistics to institutions which subscribe to the ACM Digital Library. The usage statistics are generated on a monthly basis and are made available by a third party service provider named Scholarly IQ, and library consortia can view their usage statistics at http://www.acmreports.org.

If you are having trouble logging into your institution’s account, please send us an email at dl-info@hq.acm.org and we will make sure you are given access to your institution’s statistics.

SUSHI

COUNTER 4 compliancy means that ACM’s usage statistics are also SUSHI (Standardized Usage Statistics Harvesting Initiative) compliant. SUSHI enables a library to gather their usage statistics across multiple publisher platforms without having to log into each search and compile usage statistics manually. For more information on SUSHI compliance, please go to http://www.niso.org/workrooms/sushi.

ACM Usage Reports

Standardized usage statistics are sometimes misleading. Each publisher has a different portfolio of publications with a wide range of content-types and formats available for download. In ACM’s case, the ACM Digital Library consists of non-journal and non-pdf or html content. Due to the nature of the subject matter and ACM’s role as the leading conference and scholarly events organizer in the field of computer science, the ACM Digital Library contains a significant number of conference proceedings that contribute to the overall makeup of the ACM Digital Library archive. As COUNTER 4 reports do not provide detailed usage information for conference proceedings, it is important for librarians to recognize the limitations of the COUNTER 4 reports that ACM makes available for evaluation purposes.

The reports available  at http://www.acmreports.org include the standard COUNTER 4 reports such as JR1 and JR4. However, none of these standard reports include usage for conference proceedings which are critically important to the fields of computer science and IT, and make up over two thirds (67%) of the full text articles that are included in the ACM Digital Library.

In addition, across the entire ACM Digital Library user base on average approximately 66% of its total usage occurs with ACM conference proceedings articles with the remaining activity being mostly related to ACM journal articles. To view all of the usage of the ACM Digital Library, it’s important to review the report entitled ‘Article Titles: Article Requests by Month and Type’. This report will show the total full-text downloads across all the media types that are in the Digital Library on a monthly basis.

FAQs

If you have any questions regarding the ACM usage statistics that are not answered above, please refer to our FAQs page. http://www.acmreports.org/Docs/faq.aspx.

Why I Belong to ACM

Hear from Bryan Cantrill, vice president of engineering at Joyent, Ben Fried chief information officer at Google, and Theo Schlossnagle, OmniTI founder on why they are members of ACM.

ACM Case Studies

Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.

The DevOps Phenomenon

ACM Queue’s “Research for Practice” consistently serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment of RfP is by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald, and Helmut Krcmar. Titled “The DevOps Phenomenon,” this RfP gives an overview of stories from across the industry about software organizations overcoming the early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between their software and operations teams, faster delivery times for new software features, and achieving a higher level of stability.