Difference between revisions of "PREMIS metadata: rights"

From Archivematica
Jump to navigation Jump to search
Line 9: Line 9:
  
 
== PREMIS xml view ==
 
== PREMIS xml view ==
 +
 +
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.
  
 
[[File:copyright.png|680px|thumb|center|]]
 
[[File:copyright.png|680px|thumb|center|]]
Line 35: Line 37:
  
 
[[File:license.png|680px|thumb|center|]]
 
[[File:license.png|680px|thumb|center|]]
 +
 +
= Policy-based =
 +
 +
== Data entry view ==
 +
 +
[[File:7.png|680px|thumb|center|]]
 +
[[File:8.png|680px|thumb|center|]]
 +
 +
== PREMIS xml view ==
 +
 +
[[File:policy.png|680px|thumb|center|]]

Revision as of 11:52, 19 September 2011

Main Page > Development > Development documentation > Metadata elements > PREMIS metadata: rights

Copyright-based

Data entry view

1.png
2.png

PREMIS xml view

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.

Copyright.png

Statute-based

Data entry view

3.png
4.png

PREMIS xml view

Statute.png

License-based

Data entry view

5.png
6.png

PREMIS xml view

In this example, the PREMIS fields LicenseIdentifieType, licenseIdentifierValue and licenseTerms are populated automatically by Archivematica when the object is ingested with a related licence.txt file (i.e. from a DSpace export).

License.png

Policy-based

Data entry view

7.png
8.png

PREMIS xml view

Policy.png