How Library Licensing Works | Ebooks, Databases and Access Rights

A printed book can sit on a library shelf for decades after the invoice has been paid.

A digital book can disappear from a user’s reach even though the library paid for access last year.

That difference is one of the defining mechanics of the modern library.

Digital collections are not governed only by ownership. They are governed by licences: contracts that define who may use a resource, from where, for how long, on how many devices, under what technical controls, for which purposes, and what remains after the agreement ends.

This article is part of eduKateSG’s How X Works programme and the How a Library Works series.

The shortest useful answer

Library licensing works by replacing some of the freedoms associated with physical ownership with negotiated contractual permissions and restrictions.

The library pays for a defined bundle of rights. The licence specifies the boundary of that bundle.

That boundary may determine:

who counts as an authorised user;
whether access works on-site, remotely or both;
how many people may use the resource at once;
whether material can be downloaded, printed or copied;
whether parts may be shared through interlibrary loan;
whether the library may preserve a copy;
whether text and data mining is allowed;
what user data the vendor collects;
what happens when the subscription ends;
whether access survives if the platform or supplier changes.

Licensing therefore does not merely purchase content.

It engineers access.

Ownership and access are different states

Physical collections trained generations of users to think of acquisition as ownership.

The library buys the book. The book becomes part of the collection. The library controls where it is shelved, how it is circulated, when it is repaired and when it is withdrawn, subject to law and institutional policy.

Digital resources often work differently.

The library may never receive a permanent local copy. It may instead receive permission for its users to enter a vendor platform for a defined period.

This creates two separate questions:

Does the library control the intellectual resource?
Does the library currently have permission to reach the resource?

A modern collection can therefore contain resources that are fully visible in the catalogue but conditionally reachable through contractual infrastructure.

This is one reason library acquisition and licensing are related but not identical. Acquisition decides whether the resource should enter the library’s capability portfolio. Licensing determines the contractual form of that entry.

The licence is a machine-readable idea expressed in legal language

A licence looks like a contract.

Operationally, it is also a rules engine.

Every clause can become a real system behaviour.

“Authorised users” becomes an authentication rule.
“Three simultaneous users” becomes a concurrency limit.
“No systematic downloading” becomes a monitoring rule.
“On-site access only” becomes a network-location restriction.
“No interlibrary loan” becomes a resource-sharing boundary.
“Perpetual access to subscribed years” becomes a preservation and continuity obligation.

The licence therefore sits between policy and software.

When the contract is poorly understood, the technology can enforce the wrong thing. When the technology is poorly configured, the library can accidentally breach the contract or deny users rights the contract actually permits.

Who is an authorised user?

One of the first licensing questions is identity.

A licence may define authorised users as current students, faculty, employees, members, registered borrowers, walk-in users or another defined community.

The distinction matters because the library’s community and the vendor’s permitted community may not be identical.

A university may wish to serve alumni. The licence may cover only current staff and students. A public library may welcome visitors from anywhere, but a database licence may be limited to registered local members. A research library may allow walk-in consultation while restricting remote authentication to institutional affiliates.

The licence therefore turns membership categories into access categories.

Authentication proves eligibility

Once the contract defines authorised users, technology has to identify them.

Libraries may use institutional logins, library accounts, IP authentication, proxy systems, federated identity or vendor accounts.

The mechanism is simple in principle:

The user requests the resource.
The system checks whether the user belongs to an authorised category.
The system transmits enough evidence to the vendor to permit access.
The vendor opens the resource according to the licence.

The difficult part is minimising how much personal information has to travel during this verification.

This connects licensing directly to library privacy.

Remote access is a contractual capability

Remote access feels normal in digital libraries, but it is not automatic.

The library needs both technical infrastructure and contractual permission.

A resource may be:

available anywhere to authenticated users;
available only from recognised institutional networks;
available on-site to walk-in users but not remotely;
limited by region or jurisdiction;
available through an individual account created under institutional entitlement.

When licensing and authentication are designed well, the user experiences one click.

Behind that click sits a chain of identity, entitlement, network routing and contractual interpretation.

Simultaneous-user limits recreate scarcity digitally

A digital file can technically be copied at almost zero marginal cost.

A licence can still impose scarcity.

An ebook may be licensed for one user at a time, three users at a time, unlimited users or another concurrency model.

This changes the service mechanics.

A one-user licence behaves like one physical copy. When the slot is occupied, another user waits. An unlimited-user licence behaves more like a digital utility: many users can enter simultaneously.

The library therefore buys not only content but capacity.

High-demand course readings, examination materials or popular ebooks can become queueing problems even when there is no physical object to queue for.

Licence models change the economics of the same book

The same ebook title can appear under different licensing models.

A library may encounter:

one-copy/one-user licences;
limited simultaneous-user licences;
unlimited-user licences;
time-limited licences;
usage-limited licences;
subscription access;
evidence-based or demand-driven models;
perpetual-access purchases with platform fees.

The cheapest model depends on expected use.

A low-use specialist title may not justify an unlimited-user licence. A heavily assigned textbook may become frustrating under one-user access even if the headline price is lower.

Licensing is therefore partly a demand-capacity problem.

Subscription access and perpetual access are not the same

A subscription usually provides access while the subscription remains active.

Perpetual access means the library retains continuing rights to defined content even after the active subscription ends, subject to the contract and delivery arrangement.

This distinction is fundamental.

Suppose a library subscribes to a journal for ten years and then cancels.

One licence may say access to all ten subscribed years disappears. Another may say the library keeps rights to the years already paid for but loses new issues. A third may require continuing platform fees for the archival access mechanism.

The collection’s future state therefore depends on clauses written years earlier.

This is why library funding and licensing must be considered together.

The post-cancellation question

Every recurring digital licence should answer one question clearly:

What exactly remains if we stop paying?

The answer may include:

nothing;
previously purchased titles;
subscribed years;
locally downloaded archival files;
continuing access through the same platform;
access through a preservation service;
metadata only;
rights that survive but require a new delivery mechanism.

This is the licensing return path.

A library that does not understand the return path can mistake rented reachability for durable ownership.

Platform dependence can separate rights from practical access

A licence can promise access while a vendor platform supplies the technical delivery.

If the platform disappears, changes ownership, suffers an outage or stops supporting an old product, the library may hold contractual rights but lack a functioning route to the files.

Strong licences therefore consider delivery continuity, data portability and alternative access mechanisms.

The deeper principle is the same one found throughout the Library Works series:

Identity, entitlement and route are different layers.

A resource can remain legally entitled to the library while the delivery route fails.

Digital rights management is the technical enforcement layer

Digital rights management, or DRM, can enforce restrictions on copying, printing, downloading, lending duration or device use.

The licence defines the permitted behaviour. DRM often enforces it technically.

This can create friction.

A user may be legally entitled to read a work but unable to use a preferred device. A screen reader may interact poorly with the platform. A download may expire. Copying a short quotation may be technically blocked even where the use would otherwise be lawful.

Libraries therefore evaluate not only the legal licence but the user experience created by the enforcement technology.

Printing and downloading clauses become research limits

Licences often distinguish between ordinary scholarly use and systematic extraction.

A user may be permitted to download an article for personal study but prohibited from downloading an entire database in bulk.

The boundary matters because modern research increasingly uses computational methods.

What looks like excessive downloading to a security system may be legitimate text and data mining by a researcher.

Licensing needs to distinguish malicious extraction from authorised research workflows.

Text and data mining changes the meaning of “use”

Traditional library use assumes a human reads one item at a time.

Text and data mining may involve software analysing thousands or millions of documents.

The user is not necessarily trying to read every article. They may be extracting patterns, entities, frequencies, relationships or trends across a corpus.

A licence designed only for human reading can become an obstacle to computational scholarship.

Modern licensing therefore increasingly needs explicit answers about:

automated retrieval;
API access;
bulk downloading;
temporary local copies;
derived data;
model training;
redistribution of analytical outputs.

The licence is no longer only about who can open a PDF.

AI creates new licensing questions

Generative AI adds another layer.

A library may want to use licensed collections for retrieval-augmented generation, summarisation, semantic search, entity extraction or model evaluation.

The contract may not have been written with these uses in mind.

Important questions include:

May licensed content be sent to an external AI provider?
May the provider retain prompts or source passages?
May outputs contain substantial parts of the source?
May embeddings be stored?
May the material be used to train a model?
May authorised users query the corpus through a conversational interface?
Does the licence distinguish transient processing from permanent copying?

AI therefore turns old access agreements into new interpretation problems.

The safe principle is simple: do not assume a new technical capability automatically creates a new contractual right.

Interlibrary loan tests whether access can travel

Physical libraries can often lend items to one another through interlibrary loan.

Digital licensing can complicate that tradition.

A licence may permit delivery of one article to another library under defined conditions. Another may prohibit resource sharing entirely. Another may permit printed delivery but restrict electronic transfer.

The library therefore needs to know whether access rights stop at the institutional boundary.

A collection can be rich locally and weak as part of the wider library network if licences prevent lawful sharing routes.

Course reserves and teaching use

Academic libraries frequently support teaching through course reserves, reading lists and learning platforms.

Licences can affect whether a resource may be linked, embedded, downloaded, copied into a learning environment or made available to a class.

A title that looks ideal pedagogically can be operationally unsuitable if the licence allows only one simultaneous user during an examination period.

Teaching support therefore requires licensing analysis as well as collection selection.

Walk-in users reveal the public boundary of institutional licences

Some libraries serve both a defined membership and the wider public.

A licence may permit on-site access for walk-in users even when remote access is restricted to institutional members.

This creates a useful distinction:

the user is not part of the institution;
the user is physically inside an authorised location;
the licence grants access because place substitutes for membership.

In this model, the library building itself becomes part of the authentication system.

Geographic restrictions

Digital resources are globally reachable in technical terms.

Licences may still impose geographic limits.

Rights can differ by country or region because publishers distribute rights differently, legal frameworks vary or commercial agreements are territorial.

A global university or cross-border consortium therefore needs to understand whether one agreement actually covers all intended users.

Digital reach does not automatically erase legal geography.

Accessibility clauses can determine whether licensed content is usable

Accessibility should be examined before contract signature.

A resource can contain excellent content and still be unusable for some users because the platform blocks screen readers, keyboard navigation, magnification, captions or accessible downloads.

The licence can help by requiring accessibility standards, remediation routes, documentation and reasonable cooperation when barriers are discovered.

This is an important procurement principle:

Accessibility is easier to negotiate before purchase than after dependency forms.

Privacy clauses matter because vendors can see reading behaviour

A vendor-hosted platform may observe searches, downloads, session length, device information, account identity and other behavioural data.

The library therefore needs to understand:

what data is collected;
why it is collected;
how long it is retained;
whether it is shared;
whether it is used for advertising, profiling or product development;
whether users must create personal accounts;
what happens to data after termination.

A low-cost licence can create a high privacy cost.

Price and privacy therefore belong in the same acquisition decision.

Data protection obligations flow through the contract

When a vendor processes personal data on behalf of the library or institution, the contract may need to define responsibilities around security, breach notification, subprocessors, retention, international transfer and deletion.

The exact legal requirements vary by jurisdiction.

The system principle is stable:

Outsourcing the platform does not automatically outsource institutional responsibility.

Usage statistics are both evidence and surveillance risk

Libraries need usage statistics to evaluate cost and demand.

Vendors may provide counts of searches, sessions, downloads and turnaways.

These metrics help with funding and renewal decisions.

But useful aggregate statistics do not necessarily require permanent person-level histories.

Licensing and platform configuration should distinguish service measurement from unnecessary user surveillance.

Usage caps and excessive-use clauses

Some licences prohibit unusually high-volume or systematic use.

This protects vendors against database harvesting or redistribution.

The challenge is that legitimate research can resemble abuse.

If one user downloads thousands of records for computational analysis, the platform may automatically suspend the whole institution.

Good licensing defines escalation and investigation procedures rather than making every anomaly an immediate collective punishment.

Security obligations are mutual dependencies

The library may promise to protect credentials and prevent unauthorised use.

The vendor should protect the platform, content and user data.

A secure licensing relationship therefore has obligations on both sides.

The library should not share credentials carelessly. The vendor should not expose user activity through weak security.

Security clauses make those responsibilities explicit.

Service levels convert reliability into contract language

A digital resource is useless when the platform is unavailable.

Service-level terms can address uptime, maintenance windows, support response, incident handling and communication.

Not every library licence contains detailed service guarantees, but reliability remains part of the economic value.

A cheaper platform that fails during examination periods may cost the institution more in staff time, user frustration and emergency work than the invoice suggests.

Content can change inside a licensed package

Physical ownership stabilises the object.

Licensed digital packages can change underneath the subscription.

Titles may be added, removed, transferred to another publisher or replaced.

This means the library can pay for “the database” while the actual content set changes over time.

Strong collection management therefore tracks title changes, not only the package name.

The package is a moving collection.

Package deals can hide duplication

Libraries may license large bundles containing hundreds or thousands of journals, ebooks or media titles.

The bundle can be cheaper than buying each high-value title separately.

It can also contain substantial overlap with other packages.

Licensing analysis therefore examines:

unique titles;
duplicate titles;
usage concentration;
price growth;
cancellation rights;
content movement;
perpetual-access coverage.

A package can look large while adding little unique capability.

Big deals trade flexibility for scale

Large multi-title agreements can deliver broad access at negotiated prices.

They can also lock a large portion of the collection budget into one commitment.

This creates a portfolio effect.

As recurring commitments grow, the library has less freedom to respond to new disciplines, new publishers or changing user needs.

Licensing therefore shapes future budget flexibility, not merely current access.

Consortial licensing changes bargaining power

Library consortia can negotiate licences collectively.

This can improve pricing, standardise terms and increase leverage.

It also creates additional complexity.

Members may differ in size, mission, geography, user population and technical infrastructure. A licence that works for one member may create problems for another.

Consortial licensing therefore needs both collective bargaining and local-fit analysis.

The cheapest consortium term is not always the best term

A consortium may secure a lower price by accepting restrictions that reduce member flexibility.

For example, a uniform licence may limit special walk-in access, local preservation arrangements or specialised computational research.

The network therefore asks whether the collective saving exceeds the capability lost through standardisation.

Price is one dimension of the agreement. Freedom of operation is another.

Open access changes the licensing problem but does not eliminate rights

Open-access resources are designed to be reachable without traditional subscription barriers.

That can reduce the library’s dependence on reader-side licences.

But open does not always mean unrestricted.

Open licences can still define attribution requirements, commercial-use limits, adaptation rights or share-alike conditions.

The difference is that permissions are granted more broadly in advance rather than negotiated separately by each institution.

Licensing remains present; the permission architecture changes.

Copyright and licence are different layers

A licence adds contractual permissions, restrictions and obligations between parties.

The exact interaction varies by law and contract.

The important operational lesson is that librarians should not treat every vendor restriction as a statement of copyright law, nor assume every statutory permission automatically appears unchanged inside a licence.

Licensing work requires knowing which layer is producing the rule.

Negotiation is the moment to protect future users

Once a platform becomes essential, bargaining power can decline.

Before signing, the library has the strongest opportunity to negotiate:

authorised-user definitions;
walk-in access;
remote access;
interlibrary loan;
accessibility;
privacy;
usage data;
text and data mining;
perpetual access;
termination;
data export;
governing law;
service levels;
price escalation.

Licensing is therefore preventive governance.

A good clause written early can avoid years of operational workarounds later.

Model licences reduce repeated negotiation cost

Libraries and consortia often develop preferred licence language or checklists.

These tools identify standard positions on recurring issues such as privacy, authorised users, access, preservation and termination.

The model does not remove negotiation.

It prevents the institution from forgetting important clauses each time a new vendor arrives.

Licensing knowledge becomes institutional rather than personal.

The licence register is institutional memory

A library with many digital resources can hold hundreds of active agreements.

Those agreements need structured memory.

A licence register can record:

vendor;
resource;
term dates;
renewal rules;
authorised users;
remote access;
interlibrary loan rights;
perpetual access;
privacy commitments;
accessibility clauses;
text and data mining rights;
notice periods;
price terms;
responsible staff owner.

This turns contract text into operational knowledge.

Without a register, the institution may own rights nobody remembers or violate restrictions nobody knew existed.

Renewal is a fresh acquisition decision

A licence renewal should not happen automatically merely because cancellation is inconvenient.

The library can review:

usage;
cost;
price growth;
unique content;
overlap;
user complaints;
accessibility;
privacy;
technical reliability;
new alternatives;
perpetual-access consequences.

Renewal is therefore not clerical repetition.

It is the moment when an inherited recurring commitment is placed back under conscious review.

Cancellation analysis needs a dependency map

A resource can be deeply embedded in teaching, research or public service.

Before cancellation, the library should know who depends on it and what substitutes exist.

The dependency map may include:

courses;
research groups;
clinical or technical workflows;
reference services;
linked reading lists;
downstream discovery tools;
preservation rights;
API integrations.

This helps distinguish low visible usage from low institutional importance.

Licence audits protect against accidental drift

Contracts, systems and user behaviour can drift apart over time.

A licence signed years ago may no longer match how the resource is being used today.

Periodic audits can ask:

Are current users still covered by the authorised-user definition?
Has authentication changed?
Are interlibrary-loan practices still compliant?
Has the vendor changed privacy terms?
Are preservation rights documented?
Do staff know the correct termination notice?
Has AI introduced a use the old agreement never contemplated?

An audit reconnects written agreement to observed reality.

Licence breach can affect the whole institution

A single user can sometimes trigger institution-wide consequences.

Automated bulk downloading, credential sharing or systematic redistribution can cause a vendor to suspend access for everyone.

This creates a governance problem: how should one user’s behaviour be contained without unnecessarily punishing thousands of legitimate users?

Strong incident procedures include investigation, communication, credential control, technical containment and restoration.

The contract should ideally support proportionate remediation rather than immediate permanent termination.

Termination clauses determine how the relationship ends

Every licence relationship should have an ending mechanism.

Termination terms may define:

notice periods;
termination for breach;
opportunity to cure a breach;
refunds or credits;
data return;
deletion of user data;
continuing rights;
post-cancellation access;
surviving confidentiality obligations.

This is where governance and licensing meet most clearly.

The institution should know how to leave before dependency becomes irreversible.

Governing law and dispute resolution

Licences can involve institutions and vendors in different jurisdictions.

Contracts may specify which law governs and where disputes are resolved.

This can affect practical risk and enforcement cost.

Libraries therefore review not only content clauses but the legal infrastructure of the agreement.

The exact legal effect should be assessed in the relevant jurisdiction; the systems lesson is that contract geography can matter even when content delivery is global.

Indemnity and liability allocate failure cost

Contracts often contain clauses addressing liability, warranties and indemnities.

These clauses allocate responsibility when claims, breaches, outages or misuse occur.

They may look remote from daily library service until something goes wrong.

Licensing work therefore protects not only access but the institution’s exposure when the access system fails.

Price escalation clauses shape future affordability

A licence can be affordable in year one and unsustainable in year five.

Multi-year agreements may include annual increases, fixed caps, renegotiation triggers or usage-based changes.

The library should model the future cost before accepting the present price.

This is another example of budget gravity: today’s licence commits part of tomorrow’s budget.

Currency risk can affect international licences

Libraries may purchase resources priced in foreign currencies.

Even when the vendor’s nominal price does not change, exchange-rate movement can alter the local cost.

Funding plans therefore need to distinguish vendor inflation from currency exposure.

A resource can become more expensive without the publisher changing its price.

Licence complexity creates staffing cost

The invoice is not the total cost of a digital resource.

Staff must negotiate, configure, troubleshoot, renew, interpret, audit and eventually cancel the agreement.

A cheap licence with complicated restrictions can consume substantial staff time.

Library staffing therefore includes licensing capability as part of the true operating cost of digital collections.

The licence should be understandable by operations staff

A contract that only one lawyer can interpret is not enough for daily operation.

Staff need usable summaries of the clauses that affect ordinary service.

For each resource, a practical rights summary might answer:

Who can use it?
Can they use it remotely?
Can walk-in users access it?
Can articles be sent through interlibrary loan?
Can content be used in courses?
Can users download or print?
Can researchers text-mine it?
What happens after cancellation?

This converts legal text into service instructions without replacing the contract itself.

Licence metadata can sit beside bibliographic metadata

Catalogues describe what resources are.

Licence metadata describes what users are allowed to do with them.

The two layers can be connected.

A discovery system could know that one resource is available to all members remotely while another is on-site only. A staff system could know that one journal permits interlibrary loan while another does not.

This is a powerful idea:

Rights can become structured data.

Once rights are structured, systems can help route users correctly instead of relying on memory.

Machine-readable licences are the next natural step

If contractual rights can be represented in structured form, library systems can evaluate them automatically.

A system could answer:

Is this user authorised?
Can this resource be used off-site?
May this article be supplied to another library?
Does the library retain access after cancellation?
May the corpus be mined computationally?

Human lawyers and librarians would still define and interpret the agreement.

Machine-readable rights would reduce the distance between written contract and operating system.

Licensing and digital preservation

Preservation is one of the most important differences between ownership and access.

If the library never receives a durable copy, preservation depends on the publisher, vendor or preservation network.

A strong licence can address:

local archival copies;
trusted preservation services;
post-cancellation access;
format migration;
platform failure;
vendor exit.

The preservation question is simple:

If the commercial relationship ends, can the knowledge still survive?

Licensing changes collection development

Collection development once focused heavily on choosing content.

Digital collections require choosing terms as well.

Two products may contain similar material but create very different institutional capability because one allows remote access, preservation and interlibrary loan while another restricts them.

The resource is therefore content plus rights plus delivery.

Collection quality depends on all three.

Licensing as portfolio risk

If too much of the collection depends on one vendor, platform or contract model, the library becomes fragile.

A vendor price increase, outage, merger or policy change can affect a large share of access at once.

The library therefore considers concentration risk.

How much of the collection depends on:

one publisher;
one platform;
one authentication system;
one pricing model;
one preservation route?

Diversity can be operational resilience.

Licensing decisions should scale with consequence

A small one-year licence for a low-risk resource does not require the same scrutiny as a multi-year agreement controlling a mission-critical database used by an entire university.

Review effort should increase when the agreement creates:

high financial commitment;
long duration;
large user populations;
sensitive data processing;
major preservation dependence;
technical lock-in;
significant termination cost.

This is the same governance rule applied repeatedly across the Library Works system:

Decision process should scale with consequence.

The licensing team is a cross-functional team

No single profession owns every part of a modern licence.

Depending on the agreement, review may require:

collection specialists;
acquisitions staff;
licensing experts;
legal advisers;
privacy staff;
accessibility specialists;
systems librarians;
information-security staff;
finance;
research-support teams.

The licence is therefore a coordination object.

It brings content, money, law, technology and user experience into one decision.

When licensing fails

Licensing failures often appear as service failures.

users cannot log in;
alumni lose unexpected access;
a course reading allows only one simultaneous user;
a vendor blocks the institution after unusual downloads;
screen-reader users cannot operate the platform;
the library cancels a package and discovers archival access was not retained;
an AI project cannot legally process the licensed corpus;
a privacy review discovers the platform has been collecting more user data than expected.

The root cause may sit years earlier in contract negotiation.

This is why licensing is preventive systems design.

Repairing a licensing problem

The repair depends on the layer that failed.

Confirm what the contract actually says.
Separate contractual restriction from technical malfunction.
Identify the affected users and workflows.
Check whether the vendor can grant an exception or amendment.
Repair authentication or configuration if the contract already permits the desired use.
Negotiate new terms if the existing rights are insufficient.
Document the outcome so the same ambiguity does not recur.
Feed the lesson into future licence templates and procurement checks.

The repair loop turns one contractual failure into institutional learning.

How to measure whether a licence is working

A licence should be evaluated as a service capability, not only as a contract file.

Useful signals include:

usage;
turnaways caused by simultaneous-user limits;
authentication failures;
support incidents;
cost per use;
user complaints;
accessibility failures;
privacy concerns;
content overlap;
price growth;
downtime;
preservation coverage;
staff administration cost.

No single metric defines value.

The library asks whether the licence delivers enough usable, trustworthy and sustainable access to justify the money and constraints attached to it.

Licensing as feedback control

At the system level, licensing is a feedback loop.

The library identifies a content need.
Candidate resources are compared.
Licence terms define the rights and restrictions of each option.
The institution negotiates and signs an agreement.
Authentication and platforms enforce the agreed access state.
Users produce demand, usage, complaints, failures and new forms of research.
Staff observe whether the licence still fits real use.
Renewal, amendment, cancellation or replacement changes the next state.

The licence is therefore not a document that disappears into a folder after signature.

It remains an active part of the library’s operating architecture for as long as access depends on it.

The complete mechanism

The library identifies a resource worth adding to the collection.
The supplier offers a contractual bundle of access rights.
The library defines who must be able to use the resource and how.
Licensing staff compare authorised users, remote access, simultaneous use, downloads, interlibrary loan, accessibility, privacy, preservation and computational rights.
Finance tests the price and future escalation against budget.
Technology verifies that authentication and delivery can enforce the intended rights.
The contract is negotiated and approved at a level proportionate to consequence.
Operational licence metadata is recorded so staff can understand what is permitted.
The resource enters discovery and access systems.
Usage, failures, cost and user needs are observed during the term.
Renewal places the inherited commitment back under conscious review.
Termination or cancellation follows a known return path that preserves data, rights and continuity where possible.

That is how library licensing works.

The modern library does not simply collect objects.

It collects permissions.

Those permissions determine whether the same intellectual work can be reached from home or only inside a building, by one person or ten thousand, for one year or indefinitely, by a human reader or a computational research system.

A good licence therefore does more than secure access today.

It protects the library’s ability to keep serving users when technology changes, prices rise, research methods evolve, vendors merge, platforms disappear and the collection has to make its next handoff into the future.

How Library Licensing Works | How Ebooks, Databases, Access Rights and Contracts Shape the Modern Collection