
Library databases require specific licensing for access.
That is the simple answer, and it is the one that matters first. A library does not usually “own” a database in the same way it owns a print book. It licenses access to a service, and that license sets the terms for who may use it, where it may be used, and what kind of use is allowed.
I keep coming back to that point because the word “database” hides too much. To a reader, it can sound like a stable pile of records waiting to be opened. In practice, a library database is a managed product. It comes with rules. Those rules are not a side note. They are part of what the source is.
The license can shape access in plain ways. Some databases work only for current students, staff, or faculty. Some allow off-campus login through a library or campus system. Some are limited to use inside the library building. Some permit reading and searching, but not large-scale downloading. The exact terms depend on the publisher and the library’s agreement with it.
This is why access pages matter so much. They are not just a gate. They are part of the source record. A database may look open from the outside, but the real question is whether the library has licensed it for your kind of use. That is often the first thing I check in any serious review of a digital source.
The practical fact for researchers is this: access is not the same as discovery. A database may be listed in a library catalog or on a library website, but that does not tell you the whole story. You still need to know what it covers, how it is searched, and what the license permits. Without those facts, the source can seem clearer than it is.
This is also where libraries differ from one another. One library may license a database for wide campus access. Another may license the same vendor’s product with tighter limits. A public library may offer access through a state or regional program. A special collection may allow only onsite use. The name of the database does not tell the full access story.
I think that is the part many readers miss. They ask whether a database “has” a journal, an archive, or a field of records. That is only the first layer. The second layer is whether the license gives the library the right to expose that content to its users in a given setting. If that right is narrow, the database may be useful only in a narrow way.
There is a second fact worth stating plainly. Licensing is not just about who can log in. It also shapes what the publisher allows users to do after entry. A license may limit systematic downloading, automated harvesting, posting of content elsewhere, or use outside the stated purpose. Those limits can affect research methods as much as access itself.
For humanities work, this can matter in a quiet but real way. A source that is searchable in the browser may still be poor for close comparison if its export tools are limited. A text set may be available, but only in fragments. A database may be rich in description but thin in full text. The license and the interface work together, and both need to be stated plainly.
I do not treat the publisher’s claims as the whole truth, either. A vendor page may say a database is comprehensive, easy to search, or ideal for research. That is a claim, not a full assessment. The useful question is narrower: what exactly is covered, what search tools exist, and where does the documentation admit limits? That is the ground a researcher can stand on.
The honest limit here is that licensing terms can change. A library page may be current today and outdated next term. A vendor’s access model may shift. A database may move from broad subscription access to a more restricted model, or the reverse. Without the current license text or the library’s live access notes, no one should pretend the rule is fixed.
That uncertainty is not a weakness of careful reading. It is part of the source itself. Digital access depends on agreements, and agreements change. A strong database review says so directly. It does not pretend the label on the front page is enough.
So when someone asks about a “library database,” the plain answer is that it is usually a licensed source, not a free public object. The license is what gives the library the right to provide access, and it also sets the limits of that access. For any real use, the coverage, search tools, and stated restrictions belong in the same sentence.
That is the kind of clarity The Source List aims for: one digital source worth knowing, one search tip, and one honest limitation.