Skip to content
Property · Dublin Core elements

dc rights: writing rights statements in the Dublin Core rights element

Published Formatory editorial team
http://purl.org/dc/elements/1.1/rights

Information about rights held in and over the resource.

Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. Recommended practice is to refer to a rights statement with a URI. If this is not possible or feasible, a literal value (name, label, or short text) may be provided.

Rights metadata is the field users read just before deciding whether they can reuse something, and the one catalogers most often leave as an untidy sentence. dc:rights is defined as information about rights held in and over the resource. That covers copyright notices, licenses, public domain marks, embargo or access conditions and pointers to a rights policy. The element does not prescribe a format, but DCMI’s comment does state a preference: refer to a rights statement by URI where possible.

Statements by URI

Two families of URIs cover most needs.

Creative Commons licenses and tools apply when the rights holder has chosen to license the work. https://creativecommons.org/licenses/by/4.0/ is unambiguous for any system that reads it, and CC0 and the Public Domain Mark sit alongside the licenses for dedications and labeling.

RightsStatements.org covers the far larger body of material where nobody has granted a license, which is most of what libraries and archives digitize. Its statements were designed for cultural heritage institutions and include labels such as In Copyright, In Copyright – Educational Use Permitted, No Copyright – United States and Copyright Not Evaluated. Each has a stable URI, for example http://rightsstatements.org/vocab/InC/1.0/. Large aggregators such as Europeana and the Digital Public Library of America ask contributors for one of these or a Creative Commons URI, which is a practical reason to adopt them even in a local system.

A URI by itself is not friendly to read, so display layers usually map known URIs to labels and icons. The record stores the URI, and the interface translates it.

When text is the only option

Some situations have no matching standard statement: a donor agreement with specific restrictions, a contract covering a commissioned photograph, a dataset under terms negotiated with a funder. A short literal is then acceptable. It helps to keep it short and factual (“Reproduction requires written permission from the depositor until 2040”) and to keep the full agreement in an administrative file, not in public metadata.

What does not belong in dc:rights:

  • the name of the creator, unless it is part of a copyright line
  • a disclaimer about accuracy of the content
  • technical access restrictions with no legal basis, such as “PDF only”

Splitting rights in qualified Dublin Core

DCMI Metadata Terms divides the territory. dcterms:rights has the same definition with a range of dcterms:RightsStatement. Its sub-properties narrow the meaning: dcterms:license for a legal document granting permission, and dcterms:accessRights for who may access the resource. dcterms:rightsHolder names the person or organization that owns or manages the rights.

Spread across those properties, the second example above becomes cleaner: the Creative Commons URI moves to dcterms:license and “Harbor Research Trust” becomes the rights holder, with the copyright line no longer needed as text.

Rights in a digitization chain

Rights attach to resources, and digitization creates new ones. A photograph whose copyright has expired does not become protected because a library scanned it, at least in jurisdictions that grant no new right for faithful reproductions. A record describing the scan should therefore carry the status of the underlying work, which is why the first example marks a 1910 postcard as out of copyright in the United States. Where the original comes from another collection, dc:source records that link.

The publisher and the rights holder are two separate questions as well. Many open-access articles are published by a commercial press while the authors keep the copyright, and a record that assumes otherwise misinforms anyone who checks it before asking for permission.

Example in RDF

<rdf:Description rdf:about="https://example.org/images/postcard-0412.jpg">
  <dc:title>Postcard of the pier, about 1910</dc:title>
  <dc:rights>http://rightsstatements.org/vocab/NoC-US/1.0/</dc:rights>
</rdf:Description>
<rdf:Description rdf:about="https://example.org/reports/water-quality-2024.pdf">
  <dc:rights>https://creativecommons.org/licenses/by/4.0/</dc:rights>
  <dc:rights>Copyright 2024 Harbor Research Trust</dc:rights>
</rdf:Description>

Questions about dc:rights

What does dc:rights contain?

dc:rights holds information about rights held in and over the resource: a copyright statement, a license, a public domain mark, access conditions or a reference to a rights statement. DCMI recommends a URI pointing to a published statement where one exists.

Should dc:rights be a URI or text?

A URI is preferred because it is unambiguous and machine-actionable, for example a Creative Commons license or a RightsStatements.org statement. A short text such as a copyright line is acceptable when no suitable URI exists.

What is RightsStatements.org?

RightsStatements.org publishes a small set of standardized statements for cultural heritage material, each with a stable URI, covering cases such as in copyright, no copyright in the United States and copyright not evaluated. They are widely used by digital libraries and aggregators.

Does dc:rights name the copyright owner?

It can include the owner inside a statement, but a cleaner approach in qualified records is dcterms:rightsHolder, which names the person or organization that owns or manages the rights as a separate value.

What is the difference between dc:rights and dcterms:license?

dc:rights covers any rights information. dcterms:license is a narrower sub-property of dcterms:rights for a legal document granting permission to use the resource, such as a Creative Commons or open data license, ideally identified by URI.

More from Dublin Core elements

All 9 in this group