rightsSummary is used as a general free-text element to identify information about copyrights and property rights held in and over an asset or instantiation, whether they are open access or restricted in some way. If dates, times and availability periods are associated with a right, include them. End user permissions, constraints and obligations may also be identified as needed.

Best practice: For rights information that applies to the asset as a whole, use this element within the container pbcoreRightsSummary. For rights information that is specific to an instantiation of an asset, use it within the container instantiationRights.

rightsSummary can be contained by pbcoreRightsSummary or instantiationRights.

Usage: optional, not repeatable.

Attributes

• source – optional. The source attribute provides the name of the authority used to declare the value of the element. Different elements will use the source attribute slightly differently. For example, identifier source (required) should be the name of the organization, institution, system or namespace that the identifier came from, such as “PBS NOLA Code” or an institutional database identifier. For other elements, this might be the name of a controlled vocabulary, namespace or authority list, such as Library of Congress Subject Headings. We recommend a consistent and human readable use.
• ref – optional. Use attribute ref to supply a source’s URI for the value of the element. The ref attribute can be used to point to a term in a controlled vocabulary, or a URI associated with a source.
• version – optional. The version attribute identifies any version information about the authority or convention used to express data of this element.
• annotation – optional. The annotation attribute includes narrative information intended to clarify the nature of data used in the element. This element can be used as a notes field to include any additional information about the element or associated attributes.

Subelements

rightsSummary contains no subelements.

Examples

 
Submit any issues or suggested changes for future schema iterations by creating a ticket in our Github repository.