SUSHI protocol (Standardized Usage Statistics Harvesting Initiative)

SUSHI protocol (Standardized Usage Statistics Harvesting Initiative)
Name	SUSHI protocol (Standardized Usage Statistics Harvesting Initiative)
Title	SUSHI protocol
Developer	National Information Standards Organization
Initial release	2005
Latest release	2014
Status	Active
Genre	Data harvesting protocol

SUSHI protocol (Standardized Usage Statistics Harvesting Initiative) is an automated protocol for harvesting usage statistics from online content providers, designed to streamline reporting and analytics for libraries, consortia, and publishers. It integrates with digital systems to reduce manual retrieval of COUNTER-compliant reports and interfaces with library platforms, discovery services, and analytics tools. The protocol was developed to complement COUNTER reporting and to enable programmatic exchange between service providers such as vendors, aggregators, and institutional repositories.

Overview

SUSHI connects data producers like Elsevier, Wiley, and Springer Nature with data consumers such as OCLC, ProQuest, and EBSCO by automating retrieval of COUNTER reports, facilitating workflows used by libraries at the Library of Congress, Harvard University, and the British Library. The protocol uses web service technologies associated with SOAP, XML, and later RESTful conventions inspired by practices in Microsoft, IBM, and Oracle enterprise systems, enabling integrations with platforms including Ex Libris, Innovative Interfaces, and DSpace. Designed to operate alongside standards promulgated by the National Information Standards Organization and ANSI, SUSHI reduces manual processes that previously involved CSV exports and manual reconciliation performed by institutions like Yale University, Stanford University, and the University of Cambridge.

History and Development

SUSHI originated in initiatives led by NISO and contributors from publishers such as Taylor & Francis, platforms like JSTOR, and vendors including EBSCO Information Services and ProQuest following the early 2000s emergence of COUNTER usage reporting. Early development involved stakeholders from academic consortia such as CARL, JISC, and ARL, and technical input from standards bodies including ANSI and ISO-affiliated committees. Major revisions corresponded with expanding web service practices reflected in W3C recommendations and influenced by SOAP standards championed by Microsoft and IBM; subsequent updates aligned with RESTful trends embodied by Google and Amazon Web Services. Adoption milestones involved collaborations with national libraries and consortia including HathiTrust and the Coalition for Networked Information, culminating in formal NISO documentation and broader publisher support.

Technical Specifications

SUSHI specifies a SOAP-based web service API that transmits XML payloads to request COUNTER reports, relying on XML Schema constructs used by W3C, and security mechanisms compatible with TLS as implemented in OpenSSL and supported by Apache and Nginx. Requests reference COUNTER report names and date ranges, returning structured XML that can be parsed by systems such as Alma, Sierra, and Koha using parsers like libxml2. Authentication methods include basic and token-based schemes interoperable with identity providers like Shibboleth and OAuth implementations by Google and Microsoft Azure Active Directory. Implementations often map SUSHI outputs into analytics engines like Tableau, Splunk, and Elasticsearch for visualization and further analysis.

Implementation and Adoption

Institutions including the University of Michigan, the University of Toronto, and the National Library of Australia implemented SUSHI connectors to automate monthly harvesting from publishers such as Cambridge University Press, Oxford University Press, and Sage Publications. Library consortia like CONSER, LYRASIS, and CRKN incorporated SUSHI into consortium-level reporting workflows, while vendors like Clarivate and CrossRef provided integration points for metadata and usage analytics. Major library services and discovery layers, including Summon and Primo, support ingest of COUNTER reports obtained via SUSHI, enabling administration by library staff who manage subscriptions and licensing with vendors and funders such as the Wellcome Trust and the Andrew W. Mellon Foundation.

Use Cases and Impact

Primary use cases include automated harvesting of COUNTER reports for subscription analysis at institutions like Columbia University and bibliometric studies conducted by organizations such as Elsevier’s Scopus team and Clarivate’s Web of Science group. SUSHI has enabled more frequent, reliable usage statistics feeding into academic library decision-making, resource allocation at consortia like Big Ten Academic Alliance, and cost-per-use calculations performed by publishers and consortia negotiators. Researchers at institutions such as MIT and UC Berkeley have used SUSHI-derived data for collection development, while procurement teams in universities and government research libraries have used it for license negotiations with publishers and aggregators.

Security and Privacy Considerations

Security guidance for SUSHI implementations emphasizes TLS encryption as recommended by IETF standards and certificate management practices used by Let's Encrypt, Entrust, and DigiCert, and counsels integration with identity federations like InCommon and eduGAIN. Privacy concerns include handling of potentially sensitive institutional identifiers and IP-based filtering used by publishers such as EBSCO, Wiley, and Springer, requiring compliance with institutional policies and regional laws referenced by the European Union and U.S. agencies. Audit trails and access controls are often implemented using logging frameworks like syslog, SIEM products from Splunk and IBM QRadar, and governance models used by national archives and university IT departments.

Related Standards and Interoperability

SUSHI interoperates primarily with COUNTER reports and complements metadata standards such as DOI managed by CrossRef, OpenURL used by Ex Libris and Serials Solutions, and OAI-PMH used by repositories like arXiv and PubMed Central. It aligns with web service protocols from W3C and security frameworks from IETF, and integrates with identity and access management systems like Shibboleth and OAuth adopted by Google and Microsoft. Interoperability considerations involve mapping SUSHI outputs to analytics and reporting tools including Tableau, Power BI by Microsoft, and Kibana for Elasticsearch, and coordinating with standardization efforts from NISO, ISO, and ANSI.

Category:Information technology standards