SERU (Shared E-Resource Understanding)

SERU (Shared Electronic Resource Understanding) is a NISO Recommended Practice (NISO RP-7-2012) that lets a subscribing library and a content provider (publisher, aggregator, or other vendor) forgo negotiating and signing a bespoke license agreement for an e-resource. Instead, both parties rely on a shared set of expectations grounded in existing copyright law and standard library/publisher practice, plus the model understanding set out in the RP-7-2012 document itself, which addresses the roles of the content provider, the subscribing institution, and authorized users; the scope of permitted and restricted use; privacy and confidentiality of usage data; online performance and service provision; and archiving/perpetual access. A given e-resource transaction counts as SERU-based when both the institution and the provider have indicated, typically by each being listed in NISO's SERU Registry, that they accept SERU's terms for that transaction in place of a signed license — at which point the order can be placed and access provisioned without a license ever being drafted, routed to counsel, or countersigned.

ByCASRAI Editorial Board

· Last updated 23 Jul 2026

Ask about SERU (Shared E-Resource Understanding)

Answers are drawn from this dictionary entry and the rest of the CASRAI corpus, with a link to every source.

Answers are AI-generated from CASRAI’s own published pages and can be wrong, so check the linked sources before relying on one; your question is logged without personal data — never sold, never used to train a third-party model — to show us what CASRAI is missing, so please do not type personal or confidential details. How we use this

Worked examples

Is an instance

A university library wants to subscribe to a mid-sized aggregator database. Both the library and the vendor are already listed in NISO's SERU Registry, so the acquisitions team places the order directly on SERU terms — no license draft is exchanged, no legal review is required, and access is typically live within days rather than the weeks a negotiated license would take.

Is an instance

A smaller, non-profit journal publisher registers itself as a SERU participant precisely so that any subscribing library that also participates can acquire its content on SERU's shared terms by default. This lets the publisher avoid drafting, negotiating, and tracking a separate bespoke license for every low-value institutional subscription it sells.

Looks similar, but isn't

Not an instance

A library wants to subscribe to a clinical or otherwise high-risk database that requires non-standard terms — for example, specific data-security warranties, indemnification language, walk-in-user restrictions tighter than SERU's general expectations, or a named governing-law clause. Because these needs go beyond what copyright law and SERU's shared, generic understanding cover, the transaction still requires a fully negotiated, signed license agreement; SERU is not designed as a substitute in higher-risk or non-standard cases like this.

SERU (Shared Electronic Resource Understanding) is a NISO Recommended Practice — formally, NISO RP-7-2012, SERU: A Shared Electronic Resource Understanding — that gives libraries and e-resource providers a way to complete a subscription transaction without negotiating and signing a bespoke license agreement. Instead of a custom contract, both sides rely on a common, publicly documented set of expectations grounded in existing copyright law and standard library/publisher practice.

What SERU actually replaces

Most e-resource access today is governed by a negotiated license agreement setting out authorized users, permitted uses (interlibrary loan, course reserves, walk-in access, and so on), warranties, confidentiality, and archiving rights. Producing and reviewing that license — often on both the vendor’s and the subscribing institution’s side, sometimes with legal counsel involved on both ends — is real transaction cost, and for a large volume of comparatively low-risk, low-value subscriptions that cost can exceed what the transaction itself is worth. SERU addresses that specific problem: it is a single, shared document (RP-7-2012) that both parties can point to instead of drafting individual terms from scratch. It is a Recommended Practice rather than a full ANSI-approved standard, reflecting NISO’s tiering of less formally balloted but still practice-tested guidance.

How SERU works in practice: the Registry

SERU is opt-in on both sides. A content provider and a subscribing institution each indicate, typically by listing themselves in NISO’s SERU Registry (or otherwise mutually confirming acceptance, such as through language on a purchase order), that they are willing to transact on SERU terms. Once both parties are participating, an order for a given e-resource can be placed and fulfilled — sometimes the same day — without a license ever being drafted, routed for legal review, or countersigned, because there is no license to negotiate.

What the RP-7-2012 document covers

The recommended practice sets out shared expectations across several areas that a negotiated license would otherwise need to specify individually, including: the respective roles and responsibilities of the content provider, the subscribing institution, and authorized users; the scope of permitted and restricted use of the licensed content; privacy and confidentiality of usage data; online performance and service provision by the content provider; and archiving and perpetual access to purchased content after a subscription ends.

When SERU is not the right tool

SERU is deliberately general and is meant for the broad range of e-resource transactions where a library’s and a provider’s needs are ordinary and don’t diverge from copyright law and standard practice. It is not a substitute for a negotiated license when a transaction genuinely needs non-standard terms — for example, specific indemnification or data-security warranties, resource-specific use restrictions, or a named governing-law clause. In those cases the parties still need a fully negotiated license agreement, and SERU’s own guidance is explicit that it functions as an alternative to licensing for suitable transactions, not a universal replacement for licensing as such.

Related terms

NISO Recommended Practice (RP) — the document tier SERU (RP-7-2012) belongs to, and how it differs from a full ANSI/NISO Standard.
License Agreement — the negotiated instrument SERU is designed to let parties avoid for lower-risk transactions.
KBART — a separate NISO recommended practice addressing e-resource knowledge-base metadata quality, often used alongside SERU in a library’s e-resource workflow.
NISO Access and License Indicators (ALI) — a related NISO recommended practice for machine-readable license and access status metadata.
Copyright — the underlying legal framework SERU relies on in place of custom license terms.

Use in your systems

JATS XML <role> element

xml

<role vocab="credit"
      vocab-identifier="https://casrai.org/dictionary/"
      vocab-term="SERU (Shared E-Resource Understanding)"
      vocab-term-identifier="https://casrai.org/dictionary/term/seru-shared-e-resource-understanding" />

Schema.org DefinedTerm (JSON-LD)

json

{
  "@context": "https://schema.org",
  "@type": "DefinedTerm",
  "@id": "https://casrai.org/dictionary/term/seru-shared-e-resource-understanding",
  "name": "SERU (Shared E-Resource Understanding)",
  "identifier": "https://casrai.org/dictionary/term/seru-shared-e-resource-understanding",
  "description": "SERU (Shared Electronic Resource Understanding) is a NISO Recommended Practice (NISO RP-7-2012) that lets a subscribing library and a content provider (publisher, aggregator, or other vendor) forgo negotiating and signing a bespoke license agreement for an e-resource. Instead, both parties rely on a shared set of expectations grounded in existing copyright law and standard library/publisher practice, plus the model understanding set out in the RP-7-2012 document itself, which addresses the roles of the content provider, the subscribing institution, and authorized users; the scope of permitted and restricted use; privacy and confidentiality of usage data; online performance and service provision; and archiving/perpetual access. A given e-resource transaction counts as SERU-based when both the institution and the provider have indicated, typically by each being listed in NISO's SERU Registry, that they accept SERU's terms for that transaction in place of a signed license &#8212; at which point the order can be placed and access provisioned without a license ever being drafted, routed to counsel, or countersigned.",
  "inDefinedTermSet": "https://casrai.org/dictionary/domain/compliance-regulatory#set",
  "url": "https://casrai.org/dictionary/term/seru-shared-e-resource-understanding",
  "sameAs": [],
  "license": "https://creativecommons.org/licenses/by/4.0/",
  "publisher": {
    "@id": "https://casrai.org/#organization"
  },
  "dateModified": "2026-07-23T07:34:45",
  "inLanguage": "en"
}