An entity primarily responsible for making the resource.
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
dc:creator, the Dublin Core creator element, is one of the fifteen elements of the Dublin Core Metadata Element Set, and the one most people reach for first when they describe a file. Its job is narrow: it names the entity primarily responsible for making the resource. That entity can be a person, a group of people, an organization or an automated service. Everything that sits around the act of making (who edited it, who paid for it, who put it online) belongs to other elements.
What counts as the creator in Dublin Core
The deciding word in the dc:creator definition is primarily, and a few examples show why. For a journal article the creators are its authors. For a photograph it is the photographer, even if an agency holds the rights. For a dataset generated by an instrument or a pipeline, the creator is usually the organization or project that ran it, because the machine itself is not a meaningful agent for later users of the record.
Grey areas are common in digital collections. A digitized letter has a historical author and a modern scanning project; the letter’s author is the creator of the intellectual content, while the digitization is better recorded as provenance (for example in dcterms:provenance or a separate technical record). Keeping that line clear stops the scanning lab from appearing as the author of a nineteenth-century manuscript in search results.
Recording names consistently
For the Dublin Core creator, the standard does not prescribe a name format, so consistency has to come from local practice. The common convention in libraries and archives is inverted personal names (“Lee, Ana”) and the full official form of organizations (“California State Library”, not an acronym). Whatever convention is chosen, it should be applied to every record in the collection; a mix of “A. Lee”, “Ana Lee” and “Lee, Ana” splits one person into three for any system that aggregates by creator.
Where a controlled form exists, it is worth using. Authority files such as the Library of Congress Name Authority File, VIAF or ORCID give each person or organization a stable identifier and a preferred spelling, and they resolve ambiguous names that a plain string cannot.
dc:creator, dcterms:creator and contributor
The original element lives in the namespace http://purl.org/dc/elements/1.1/. Its twin in the DCMI Metadata Terms namespace, dcterms:creator, carries the same definition but adds a formal range: its value is expected to be an Agent, which makes it the better fit when the creator is identified by a URI instead of a text string. Many current application profiles use dcterms:creator for new linked-data work and keep dc:creator for compatibility with OAI-PMH harvesting, where simple Dublin Core remains the baseline format.
dc:contributor is the neighbor that causes most confusion. The rule of thumb: if removing the person would leave a different work, they are a creator; if the work would still exist but in a less polished form, they are a contributor. Translators are a classic edge case and are usually recorded as contributors, with the role noted where the schema allows it.
Practical checklist and examples
- One
dc:creatorstatement per creator; never pack several names into one value separated by semicolons. - Keep the order given on the resource itself (title page, credits, citation).
- Use the same name form throughout the collection, ideally taken from an authority file.
- Do not record the publisher, the depositor or the digitization project as the creator unless they genuinely made the content.
- Prefer
dcterms:creatorwith a URI when the record is published as linked data.
The RDF examples below show dc:creator repeated once per author, the most common pattern in real records.
Read together with dc:publisher, dc:date and dcterms:rightsHolder, the creator element gives a record its basic answer to “who made this, and when?”, the two questions users ask most often after “what is it?”.
Example in RDF
<rdf:Description rdf:about="https://example.org/reports/annual-2024.pdf">
<dc:title>Annual report 2024</dc:title>
<dc:creator>Lee, Ana</dc:creator>
<dc:creator>Okafor, Daniel</dc:creator>
<dc:publisher>City Library</dc:publisher>
</rdf:Description>
Questions about dc:creator
Who is the creator in Dublin Core?
The creator is the person, organization or service primarily responsible for making the resource: the author of a text, the photographer of an image, the composer of a score, or the agency that produced and released a dataset.
Can a record have more than one dc:creator?
Yes. Every Dublin Core element is optional and repeatable, so a co-authored report carries one dc:creator statement per author, ideally in the order the work itself gives on its title page, in its credits or in its preferred citation.
What is the difference between dc:creator and dc:contributor?
dc:creator names the entity primarily responsible for the content. dc:contributor covers secondary roles such as editors, translators or illustrators whose work shaped the resource without being its main authorship.
Should dc:creator hold a name or a URI?
In the legacy dc: namespace a literal name is the norm. When linked data matters, dcterms:creator with a URI pointing to an authority record (VIAF, ORCID, Wikidata, a local name authority) is the more precise choice.
Is the publisher the same as the creator?
Not necessarily. The publisher makes the resource available, while the creator made it. A university press publishing a monograph is the publisher, and the scholar who wrote it is the creator, even when both names appear together on the title page.