Every standard your library,
LMS, or AMS expects.

What it is

COUNTER (Counting Online Usage of Networked Electronic Resources) defines how platforms count and report usage of journals, books, databases, and other digital content. Version 5.1 is the current release.

Key components

• ›TR — Title Report: usage by title (most common for renewals)
• ›DR — Database Report: usage by database or collection
• ›IR — Item Report: granular usage at article or chapter level
• ›PR — Platform Report: total platform usage (required for aggregators)

Why it matters

Libraries use COUNTER reports to evaluate renewals, demonstrate value to administrators, and benchmark spend. Without COUNTER compliance, institutional subscribers cannot justify the subscription to their collections committee.

ZenPub implementation

ZenPub generates TR, DR, and IR reports automatically from every patron access event. SUSHI API (R5.1) is built in — libraries pull reports directly into their ERM systems without emailing you for spreadsheets.

What it is

SUSHI (Standardized Usage Statistics Harvesting Initiative) is a protocol that lets library ERM systems pull COUNTER reports automatically via API — eliminating the email-and-spreadsheet workflow.

Key components

• ›R5.1 JSON endpoint for TR, DR, IR, and PR reports
• ›Authentication via requestor ID and API key
• ›Date range parameters for monthly, quarterly, annual pulls

Why it matters

ERMs like Ex Libris Alma, EBSCO ERM, and OCLC WorldShare expect SUSHI endpoints. Platforms without SUSHI force librarians to download and upload spreadsheets manually — a friction point that affects renewal decisions.

ZenPub implementation

ZenPub's SUSHI R5.1 endpoint is available on Growth plan and above. Institutions add ZenPub to their ERM's SUSHI harvester list and reports pull automatically on schedule.

What it is

ONIX for Books (Online Information eXchange) is the XML format used by publishers to send metadata — title, author, ISBN, subject, pricing, rights, availability — to retailers, distributors, and aggregators. Version 3.0 is current.

Key components

• ›Product record with title, contributor, bisac subject, audience
• ›Supply detail: pricing, availability, digital rights info
• ›Collateral detail: cover images, descriptions, endorsements

Why it matters

ONIX is the language of book supply chains. Distributors, retailers (Amazon, Apple Books), library aggregators (EBSCO, ProQuest), and discovery layers (OCLC) all expect ONIX feeds. Without it, your titles don't appear where readers look.

ZenPub implementation

ZenPub accepts ONIX 3.0 feeds for bulk metadata import. Publishers can upload an ONIX feed once to populate their entire catalogue with correct metadata, pricing, and subject classification.

What it is

KBART (Knowledge Bases And Related Tools) is a tab-delimited file format that lists a platform's holdings — which titles are available, their coverage dates, and ISSNs/ISBNs — in a form library knowledge bases and link resolvers can ingest.

Key components

• ›title_url, title_id, publication_title fields per row
• ›date_first_issue_online / date_last_issue_online for serial coverage
• ›Submitted to knowledge base providers (Ex Libris, EBSCO, ProQuest)

Why it matters

Link resolvers (SFX, 360 Link, Full Text Finder) use KBART to know which URLs to resolve. Without a KBART file, library users clicking a DOI or OpenURL often get a dead-end "full text not available" message even when they have access.

ZenPub implementation

ZenPub exports a KBART-compliant holdings file updated daily. Download from your admin panel or point knowledge base providers to the auto-generated URL.

What it is

MARC (MAchine-Readable Cataloging) is the data format library OPACs use to store and display catalogue records. MARC 21 is the current version used in Alma, Koha, Sierra, and most library management systems.

Key components

• ›Fields 020 (ISBN), 245 (title), 100/700 (authors), 520 (description)
• ›856 field carries the electronic access URL
• ›Leader and control fields carry format and encoding information

Why it matters

Without MARC records, your content doesn't appear in the library's own catalogue — invisible to patrons browsing by subject or searching the OPAC. Libraries often require MARC records as a condition of subscription.

ZenPub implementation

ZenPub generates MARC 21 records exportable as MRC or XML. Exported individually per title or as a full collection set for batch loading into any ILS.

What it is

OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting) lets external systems harvest metadata from your repository on a schedule — used by discovery layers, institutional repositories, and aggregators.

Key components

• ›ListRecords verb returns DC or MARC XML metadata records
• ›GetRecord for individual item metadata
• ›Identify, ListSets, ListMetadataFormats for service discovery

Why it matters

Discovery layers (EBSCO Discovery Service, Primo, Summon) use OAI-PMH to index your content centrally. Open-access publishers use it to expose metadata to harvesters like BASE, CORE, and OpenAIRE.

ZenPub implementation

ZenPub exposes an OAI-PMH endpoint (Dublin Core and MARC XML) for all published content. Aggregators and discovery services can harvest and stay in sync automatically.

What it is

SCORM (Sharable Content Object Reference Model) defines how eLearning content is packaged and how it communicates completion, score, and progress back to the LMS. SCORM 2004 (3rd/4th edition) is the most widely deployed version.

Key components

• ›imsmanifest.xml defines the course structure and metadata
• ›SCORM API: Initialize, GetValue, SetValue, Commit, Terminate calls
• ›Tracks: completion_status, success_status, score, session_time

Why it matters

If your courses don't deliver SCORM, they can't be uploaded to corporate LMS platforms (SAP SuccessFactors, Cornerstone, Docebo, TalentLMS). SCORM is the baseline expectation for corporate and continuing education buyers.

ZenPub implementation

ZenPub hosts SCORM 2004 packages natively — upload a ZIP and the platform handles playback, tracking, and reporting. Learner completion and scores are stored in ZenPub and visible in your admin analytics.

What it is

xAPI (Experience API, formerly Tin Can) is the successor to SCORM for tracking learning experiences. Unlike SCORM (LMS-dependent), xAPI statements are sent to any Learning Record Store (LRS) — enabling tracking across apps, simulations, and offline activities.

Key components

• ›Statements: {actor} {verb} {object} — e.g. "Jane completed Module 3"
• ›Stored in an LRS (Learning Record Store) like SCORM Cloud or Watershed
• ›Supports rich metadata, team-based learning, and non-LMS contexts

Why it matters

CME providers, medical training platforms, and sophisticated L&D programmes are moving to xAPI for richer data. If you track CEUs, clinical simulations, or multi-modal learning journeys, xAPI gives you the data SCORM cannot.

ZenPub implementation

ZenPub generates xAPI statements for all content interactions. Pipe them to your LRS of choice, or use ZenPub's built-in analytics which store xAPI data natively.

What it is

LTI (Learning Tools Interoperability) 1.3 lets your content launch directly inside an LMS (Canvas, Moodle, Blackboard, D2L) with the learner already authenticated — no separate login, no SAML config per institution.

Key components

• ›Platform (LMS) registers the tool once via Dynamic Registration or manual config
• ›Launch URL delivers content in an iframe or new tab
• ›Advantage services: Assignment & Grades (AGS), Names & Roles (NRPS), Deep Linking

Why it matters

Universities that embed your courseware in Canvas or Moodle need LTI. Without it, instructors must copy content URLs manually and students must log in separately. LTI 1.3 with Advantage makes your content a first-class citizen in any LMS.

ZenPub implementation

ZenPub is an LTI 1.3 Advantage-compliant tool provider. Add ZenPub to your institution's LMS once; instructors can then deep-link individual courses or resource pages into their course shells.

What it is

OpenAthens is a federated identity service used by 4,000+ libraries, hospitals, and professional associations. Members authenticate via their institution's OpenAthens account and get seamless access to subscribed resources — no per-user registration.

Key components

• ›SAML 2.0-based federation managed by OpenAthens Ltd
• ›Publisher joins OpenAthens SP catalogue; institutions subscribe to publisher
• ›Walkin access, IP fallback, and guest access all configurable

Why it matters

NHS hospital trusts, UK universities, and many society members authenticate exclusively via OpenAthens. Without it, these users cannot access your platform even if their institution has a subscription — the friction usually means they don't bother.

ZenPub implementation

ZenPub is an OpenAthens service provider. Publishers on the platform are immediately available to any institution that subscribes via the OpenAthens catalogue. Setup takes minutes, not a week of SAML debugging.

What it is

SAML (Security Assertion Markup Language) 2.0 is the XML-based standard for single sign-on between an identity provider (university, employer) and service providers (publishers, platforms). Shibboleth is the most common SAML IdP in academia.

Key components

• ›SP-initiated: user arrives at platform, redirected to IdP, assertion returned
• ›IdP-initiated: user clicks link in university portal, lands at platform already authenticated
• ›Attributes: eduPersonPrincipalName, mail, eduPersonEntitlement, affiliation

Why it matters

Enterprise and academic institutions require SAML 2.0 for IT compliance — they will not allow passwords stored outside their identity provider. SAML is a precondition for any large institutional deal.

ZenPub implementation

ZenPub supports SAML 2.0 SP configuration per tenant. Add your institution's IdP metadata and map attributes in the admin panel — no code, no professional services required.

What it is

IP-range authentication grants access to any user whose request comes from an IP address within a registered range — typically a library building, campus network, or VPN. No login required.

Key components

• ›IPv4 and IPv6 CIDR ranges registered per institution
• ›Access granted silently — patron sees no login prompt
• ›Often combined with SAML/OpenAthens for off-campus access

Why it matters

Public and academic libraries require IP-range access for walk-in patrons who cannot be expected to have a university login. It is the lowest-friction access method and a minimum requirement for library subscriptions.

ZenPub implementation

Register unlimited IP ranges per institutional subscriber in the ZenPub admin panel. Access is enforced at the middleware layer before any page renders.

What it is

Readium LCP (Lightweight Content Protection) is the open DRM standard governed by EDRLab and supported by Readium Foundation. It encrypts EPUB files with per-license keys tied to the user's passphrase — readable in Thorium, Aldiko, and other LCP-compatible readers.

Key components

• ›AES-256 CBC encryption on EPUB content
• ›License document: encrypted content key, rights (copy, print, loan dates), links
• ›User passphrase hashed with PBKDF2; never transmitted in cleartext

Why it matters

Publishers distributing EPUBs through libraries (OverDrive, Bibliotheca) or direct-to-library expect DRM to prevent unlimited copying. Readium LCP is increasingly preferred over Adobe DRM because it is open, cheaper to implement, and works with more readers.

ZenPub implementation

ZenPub implements Readium LCP natively using an EC P-256 private key stored as a platform secret. EPUB files are encrypted on upload; licenses are generated per-access with configurable loan periods, copy limits, and print quotas.