Is a Database a Title? Understanding How Databases Are Named, Cited, and Classified
If you’ve ever tried to cite a database in an academic paper, format a bibliography entry for an online resource, or simply wondered whether the name of a database deserves special formatting treatment, you’re not alone. The question “is a database a title?” sits at the intersection of writing style, academic citation practice, and information science, and it trips up students, researchers, writers, and professionals more often than you might expect.
The short answer is yes — a database is considered a title, and in most major style guides it is formatted accordingly. But the longer answer is far more interesting, because it touches on what a database actually is, how titles function as a category in language and publishing, and why the rules around naming and citing databases exist in the first place. Let’s dig into all of it.
What Is a Database, Really?
Before exploring whether a database qualifies as a title, it helps to understand what a database is in the context we’re discussing. In everyday computing, a database is a structured collection of data organized for easy retrieval. Think of a spreadsheet on a vast scale — rows, columns, relationships, and queries working together to store and surface information.
But in the world of research, libraries, and academic publishing, the word “database” typically refers to something a bit more specific: a curated, searchable collection of records, articles, references, or other content made available through a platform or service. Examples include JSTOR, PubMed, ProQuest, Scopus, LexisNexis, ERIC, and hundreds of others. These are platforms that aggregate published works, data, or records and make them accessible — usually to subscribers such as universities, hospitals, law firms, or individual researchers.
This kind of database has a name, a publisher or provider, a subject scope, and a defined purpose. It is, in every meaningful sense, a work — a product of intellectual and editorial effort that has been assembled, maintained, and branded. That context is what makes the title question both sensible and important.
What Makes Something a “Title”?
In writing and publishing, the word “title” doesn’t just refer to the name of a book or movie. It refers to the name of any work or distinct creative, editorial, or intellectual product. Style guides like the Chicago Manual of Style, the APA Publication Manual, and MLA Handbook have developed detailed systems for distinguishing between different types of works and formatting their titles accordingly.
The basic distinction most people learn early is between works that stand alone and works that are part of a larger whole. A novel is a standalone work; a short story published in an anthology is part of a larger whole. A full-length film is standalone; an episode of a television series is part of a larger whole. For standalone works, titles are italicized (in most modern style guides) or underlined (in older practice). For works that are parts of larger wholes, titles are placed in quotation marks.
Databases fit into this system as containers — large, standalone works that hold many smaller works within them. They are more like the anthology than the short story, more like the journal than the individual article. They are platforms, collections, and reference works all rolled into one. And because they are substantial, named, independently published works, their names are treated as titles.
How Major Style Guides Handle Database Titles
APA Style
The American Psychological Association’s style guide is one of the most widely used in the social sciences, education, and nursing. In APA 7th edition, when you retrieve a source from a database, you generally do not need to include the database name in your reference unless the source would be difficult to find otherwise — for example, if it’s a dataset or a specialized record available only through that specific platform.
When the database name is included, it is not italicized in APA style. Instead, it appears as plain text. For example: “Retrieved from PsycINFO.” This might seem to contradict the idea that database names are titles, but APA’s approach reflects a pragmatic choice: since most sources can be found through multiple databases, the database is treated more like a location than a work in its own right.
However, when citing databases directly — for example, when you are using the database itself as a source, or when citing a dataset or record that exists only within a specific database — APA does treat it with the conventions appropriate to a titled work, and the name takes on a capital-letter treatment that signals its identity as a proper name.
MLA Style
The Modern Language Association’s handbook, widely used in humanities disciplines, takes a somewhat different approach. MLA format uses a “containers” system introduced in its 8th and 9th editions. Under this framework, a database is literally called a “container” — it is the larger work within which the source you are citing lives. Container titles in MLA are italicized.
So in MLA format, if you retrieve an article from JSTOR, JSTOR appears in your Works Cited entry as an italicized container title. The same applies to other databases: EBSCOhost, ProQuest, PubMed, Gale, and so on. These names are formatted the same way a journal or book series would be formatted, because they serve the same function in the citation: they tell your reader where the source lives and who the publisher of that container is.
This is a clear and explicit answer to the question. In MLA, yes, a database is a title — specifically, a container title — and it is italicized accordingly.
Chicago Style
The Chicago Manual of Style, used heavily in history, the arts, and many professional publishing contexts, also treats database names as titles. In Chicago notes and bibliography style, as well as in Chicago author-date format, databases are italicized when they appear in citations. A database like ProQuest Historical Newspapers or Oxford English Dictionary Online is italicized just as a book or journal would be.
Chicago’s treatment is particularly illuminating because it is one of the most comprehensive style systems in existence, and its handling of electronic and digital resources has been carefully developed over successive editions to account for the realities of online research. The style guide explicitly recognizes that databases function as works, and it treats their names with the same typographical respect it extends to any published, titled work.
Why It Matters: The Purpose Behind Formatting
You might wonder why any of this matters. After all, whether or not you italicize the word “JSTOR” in a bibliography doesn’t change the content of your paper. But the conventions of title formatting exist for good reasons, and understanding those reasons makes the rules easier to follow and remember.
Formatting a name as a title signals to the reader that this word or phrase is the proper name of a work — not just a description, not a category label, but a specific, branded, identifiable entity. When you write “I found this article in a database,” the word “database” is a common noun. When you write “I found this article in JSTOR,” the word “JSTOR” is a proper noun referring to a specific, named work. Italicizing or otherwise marking it signals that distinction.
This matters for citation because citations are meant to be reproducible. A reader following your citation should be able to find the same source you used. Knowing which database you retrieved something from can be crucial — particularly for datasets, legal records, archival materials, newspaper archives, and other sources that may not be universally accessible. The formatting conventions that treat database names as titles are part of the larger system for making citations precise, verifiable, and useful.
Database Names as Proper Nouns and Branded Titles
Even outside the formal world of citation style, database names function as titles in the way we use language. They are proper nouns. They are branded. They carry meaning and identity.
JSTOR is not just “a database of academic journals.” It is a specific organization with a specific collection, a specific interface, a specific history, and a specific mission. PubMed is not just “a medical literature database” — it is the National Library of Medicine’s specific, curated, searchable index of biomedical and life sciences literature. These names are titles in the truest sense: they are the names by which unique works are identified and distinguished from all other works of a similar type.
This is exactly how we treat the titles of books, films, newspapers, and journals. The New York Times is not just “a newspaper.” The Encyclopedia Britannica is not just “an encyclopedia.” We capitalize and format these names because they refer to specific, identifiable works, and we do the same for databases.
Common Situations Where This Comes Up
Academic Research Papers
The most common context where people encounter this question is when writing research papers that require citations. If you are a student using databases like Academic Search Complete, ProQuest Central, or PsycINFO, you will likely need to include those database names in your citations depending on your instructor’s style guide preferences. Knowing that they function as titles helps you format them correctly — italicized in MLA and Chicago, typically plain text in APA, but always capitalized as proper names.
Library and Information Science
Librarians and information professionals think about databases constantly. When they write guides, tutorials, course materials, or institutional documentation, they routinely refer to databases by name. In professional library literature, database names are treated as titles and formatted accordingly. Understanding this convention is part of professional practice in library and information science.
Technical Documentation and Data Science
In a more technical context, “database” often refers to a SQL database, a NoSQL system, a relational database management system, or a proprietary data system with a specific name — Oracle Database, Microsoft SQL Server, MongoDB, PostgreSQL. These names are also, in a meaningful sense, titles: they are the proper names of specific products. In technical writing, they are capitalized and treated as brand names.
Publishing and Indexing
Databases that index scholarly literature, such as Web of Science, Scopus, or the Directory of Open Access Journals, are frequently referenced in academic publishing contexts — for example, when authors note where a journal is indexed. In those contexts, the database names function exactly as titles: they are the identifiers by which specific indexing services are known and distinguished.
Practical Tips for Formatting Database Names
If you’re writing a paper or document and need to format database names correctly, here are the practical takeaways based on what we’ve covered.
In MLA format, always italicize database names when they appear as container titles in your Works Cited list. If you are writing about a database by name in the body of your text — for instance, discussing your research methodology — it is generally consistent to italicize there as well.
In Chicago style, italicize database names in footnotes, endnotes, and bibliographic entries. When referring to a database in body text, capitalize the name as a proper noun and italicize it for consistency with the style guide’s treatment of titles.
In APA style, capitalize the database name as a proper noun, but follow APA’s specific guidance on when to include it at all. In most cases, APA 7th edition prefers that you include a DOI rather than a database name, using the database name only when a DOI is not available and when the source is difficult to locate otherwise.
When in doubt, capitalize. Whatever formatting choices you make, the most important thing is to capitalize database names consistently, because they are proper nouns. Lowercase treatment — writing “jstor” or “pubmed” — would be incorrect regardless of which style guide you are following.
Databases as Intellectual Works Deserving Recognition
There’s a broader point worth making here. Treating database names as titles is not merely a typographical convention. It reflects something meaningful about how we understand databases as intellectual products. The people who build, curate, license, and maintain major research databases invest enormous resources in creating tools that make knowledge more accessible. JSTOR’s collection represents decades of digitization work. PubMed’s index is the product of continuous, expert curation by the National Library of Medicine. Recognizing these databases with the same title treatment we extend to books and journals is a small but real acknowledgment of their status as significant intellectual works.
When you cite a database, you are not just providing a retrieval location. You are acknowledging a specific resource that shaped your research, granting your reader the information they need to evaluate and replicate your work, and situating your scholarship within the ecosystem of resources that made it possible. Formatting the database name as a title is part of treating that acknowledgment with the care it deserves.
Conclusion
So, is a database a title? Yes. In the context of research, writing, and citation practice, a database is a titled work — a named, published, identifiable resource that functions as a container for other works or as a standalone reference resource. Major style guides treat database names as titles, with MLA and Chicago italicizing them and all guides capitalizing them as proper nouns.
Whether you are a student working on a term paper, a researcher preparing a manuscript, a librarian writing instructional materials, or a professional documenting sources in a technical report, the answer is clear: the name of a database is a title, and it deserves to be treated as one. Apply that principle consistently, consult your relevant style guide for the specific formatting rules, and your citations will be cleaner, more accurate, and more professionally presented for it.
