Difference between revisions of "PREMIS metadata: rights"
Jump to navigation
Jump to search
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > [[Metadata elements]] > PREMIS metadata: rights | [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > [[Metadata elements]] > PREMIS metadata: rights | ||
| + | |||
| + | '''This right module is implemented in Archivematica 0.8. For 0.10 rights requirements see [[PREMIS metadata: rights - 0.10]]''' | ||
= Copyright-based = | = Copyright-based = | ||
| Line 57: | Line 59: | ||
[[File:donor.png|680px|thumb|center|]] | [[File:donor.png|680px|thumb|center|]] | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 13:32, 10 July 2013
Main Page > Development > Development documentation > Metadata elements > PREMIS metadata: rights
This right module is implemented in Archivematica 0.8. For 0.10 rights requirements see PREMIS metadata: rights - 0.10
Copyright-based[edit]
Data entry view[edit]
PREMIS xml view[edit]
In this example, the linkingAgentIdentifier container has been populated, which means that an agent was created when the user filled in the Rights holder field in the data entry template.
Statute-based[edit]
Data entry view[edit]
PREMIS xml view[edit]
License-based[edit]
Data entry view[edit]
PREMIS xml view[edit]
In this example, the PREMIS fields LicenseIdentifieType, licenseIdentifierValue and licenseTerms are populated automatically by Archivematica when the object is ingested with a related licence file (i.e. from a DSpace export).
