An entity responsible for making the resource available.
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
The publisher answers a different question from the creator. dc:creator records who made the resource; dc:publisher records who made it available. For a printed monograph the two are easy to separate: the author writes it, the press publishes it. For digital resources the line blurs, and the same organization can produce a file, host it and announce it.
Who counts as publisher for digital material
The DCMI definition is broad enough to cover a person, an organization or a service. A few recurring cases:
- Journal articles have the journal’s publisher, even when the copy being cataloged was downloaded from a preprint server or a university repository.
- Government reports are usually published by the issuing agency. If a printing office distributed them, catalogs differ on whether to name the office; the common choice is the agency.
- Datasets are often published by the data center or repository that assigns the DOI and provides access, which may differ from the research group that collected the data.
- Websites and blogs are published by whoever operates them. For a personal site that is the author.
- Theses and working papers first released by a university repository can name the university or the department as publisher.
The test in each case is the same. Who took the decision to release this version to the public?
Digitized copies and the repository question
Digitization creates a second resource, and catalogers disagree about whose name belongs on it. A library that scans an 1890 pamphlet and puts the images online has made the digital surrogate available, so it is arguably the publisher of that surrogate. The original pamphlet’s printer remains the publisher of the original.
Simple Dublin Core cannot express both cleanly in one record. The usual answer is to decide which resource the record describes and stick to it. A record describing the surrogate names the digitizing institution; the original’s publication details move to a source note or to dc:source. A record describing the original names the historical publisher, and the digitizing institution appears in provenance or holdings data. Mixing the two produces records in which a 2015 scanning program seems to have published something in 1890.
Recording the name
As with the creator, Dublin Core leaves the name form to local practice. The name should appear as it does on the resource, or in its authority form where the collection uses one. Place of publication does not belong inside the publisher string; “London: Example Press” is a bibliographic citation habit, and it pollutes facets. Qualified records can use dcterms:spatial or a separate local field for place, and the publisher name stays clean.
Abbreviations are the other trap. “NWB” means something inside one regional agency and nothing to a harvester, and a FOAF name or authority record exists precisely so the full form can be recorded once and reused.
Publisher, rights holder and date
The publisher is often assumed to hold the rights, and frequently does not. Authors retain copyright under many open-access agreements, and government publications may be in the public domain while still having a named publisher. dcterms:rightsHolder and dc:rights carry that information separately.
The publisher also gives meaning to the publication date. Where a record states a publisher, the matching dc:date is normally the date that publisher released the resource; a record pairing the original printer with the scan date tells users something that never happened.
Example in RDF
<rdf:Description rdf:about="https://example.org/datasets/river-gauges-2022.csv">
<dc:title>River gauge readings, 2022</dc:title>
<dc:creator>Hydrology Unit, Northern Water Board</dc:creator>
<dc:publisher>Northern Water Board</dc:publisher>
<dc:date>2023-02-14</dc:date>
</rdf:Description>
Questions about dc:publisher
Who is the publisher in Dublin Core?
The publisher is the entity responsible for making the resource available: a publishing house, a university press, a government agency releasing a report, a data center distributing a dataset or a person who self-publishes a website or a file.
Is the repository holding a copy the dc:publisher?
Usually not. A repository that stores a copy of a journal article has not published it; the journal's publisher has. Some repositories do act as publisher for material they release first, such as theses or working papers.
Can dc:creator and dc:publisher be the same?
Yes. A self-published book, a personal blog or an agency report produced and released by the same office will name the same entity in both elements. Recording it twice is correct, since each element answers a different question.
How should publisher names be recorded?
Use the name as it appears on the resource or in an authority file, written the same way across the collection. Avoid abbreviations that are ambiguous outside the institution, and do not add place of publication to the publisher string.
Is there a URI-based version of dc:publisher?
dcterms:publisher has the same definition and a range of dcterms:Agent, so it is meant to point to an agent, typically by URI. It suits linked-data records, while dc:publisher with a literal name stays common in OAI-PMH exports.