Skip to content
Property · DCMI Metadata Terms: properties

dcterms:rightsHolder: naming the rightsholder, with URIs and literals

Published Formatory editorial team
http://purl.org/dc/terms/rightsHolder

A person or organization owning or managing rights over the resource.

Recommended practice is to refer to the rights holder with a URI. If this is not possible or feasible, a literal value that identifies the rights holder may be provided.

Users looking at a photograph in an online collection tend to ask the same two questions: may this be reused, and if not, who can give permission? The first is answered by dc:rights and, where a license exists, by dcterms:license. The second is the job of dcterms:rightsHolder, which names a person or organization owning or managing rights over the resource.

Why it is a separate property

Rights statements were traditionally written as a single sentence: “Copyright 1978 Jana Novak, all rights reserved.” The sentence contains a status, a date and a name, and no system can pull them apart reliably. DCMI Metadata Terms added rightsHolder so the agent could stand on its own. The status goes in dcterms:rights, the permission in dcterms:license, and the holder in this property, ideally as a URI for an agent record.

The range is dcterms:Agent. A URI for the rightsholder can carry a name, contact details, an authority identifier and a note about the arrangement, and every record that points to it is updated when any of those change. A literal name is allowed when no agent record exists, as the comment says, but it repeats the name in every record, along with every spelling variant that creeps in.

The property has no built-in way to say which rights a holder controls. A photograph can have one rightsholder for the image and another for a logo or artwork visible in it; a recorded song separates composition from recording. Two rightsHolder statements are allowed, and a short rights note explaining the split prevents users from contacting only one party.

Creator, publisher and rightsholder

The three are easy to conflate because in simple cases they coincide. A freelance photographer who publishes on a personal website is creator, publisher and rightsholder at once. Many other cases split them:

Situation Creator Rightsholder
Work made by an employee the employee often the employer
Author has died the author heirs or estate
Rights assigned to a publisher the author the publisher
Open-access article under author-retained copyright the authors the authors

The last row is a reminder that the publisher is not automatically the rightsholder, even for commercially published work. And the holding institution is not the rightsholder simply because it owns the physical object. Owning a print and owning the copyright in the image on it are separate things, and a record that names the archive as rightsholder by default misleads anyone who relies on it for a permission request.

Recording agents well

Agent records for rightsholders follow the same practice as for creators: a stable URI, a preferred name (a foaf:name value, for example), and where possible a link to an authority file such as VIAF, ISNI or Wikidata. ISNI, an ISO standard identifier for the public identities of people and organizations involved in creative works, is especially common in publishing and music, where rights are traded most actively.

Contact details are tempting to add and quick to go stale. A link to the organization’s own contact page ages better than an email address copied into thousands of records.

Unknown and orphan cases

Many archival items have no identifiable rightsholder: anonymous photographs, letters from unknown correspondents, publications from defunct companies. Leaving dcterms:rightsHolder empty is correct in those cases. The uncertainty belongs in the rights status, where RightsStatements.org offers labels for undetermined and orphan works, and in a note recording what searches were made. Under the EU orphan works directive, a documented diligent search is a condition for certain uses, so that note can matter later.

Where a rightsholder has been found but has not responded, recording the name with a note is more useful than omitting it, since the next person asking will know where the search ended.

Example in RDF

@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .

<https://example.org/photos/market-square-1978.tif>
    dcterms:creator <https://example.org/people/j-novak> ;
    dcterms:rightsHolder <https://example.org/org/novak-estate> ;
    dcterms:rights <http://rightsstatements.org/vocab/InC/1.0/> .

<https://example.org/org/novak-estate>
    a foaf:Organization ;
    foaf:name "Estate of Jana Novak" .

Questions about dcterms:rightsHolder

What is a rightsholder in metadata?

A rightsholder is the person or organization that owns or manages rights over a resource, typically copyright. In DCMI Metadata Terms it is recorded with dcterms:rightsHolder, ideally as a URI pointing to a description of that agent.

Is the rightsholder the same as the creator?

Often but not always. Copyright can belong to an employer for works made in employment, pass to heirs after death or be assigned to a publisher. The creator made the work; the rightsholder controls it now.

What is the range of dcterms:rightsHolder?

The range is dcterms:Agent, a resource that acts or has the power to act, such as a person or organization. That is why the recommended value is a URI for the agent, with a literal name as the fallback.

Can dcterms:rightsHolder include 'managing' organizations?

Yes. The definition covers agents owning or managing rights, so a collecting society, a literary agency or an archive administering rights on behalf of an estate can be named, provided the record makes the actual arrangement clear in a rights note.

What should be recorded if the rightsholder is unknown?

Leave the property out and say so in the rights statement, for example with a RightsStatements.org label for undetermined or orphan works. Guessing a rightsholder, or naming the holding institution by default, gives users false information about whom to ask.

More from DCMI Metadata Terms: properties

All 13 in this group