PREMIS metadata in Archivematica¶

Archivematica supports PREMIS metadata and currently implements version 3. It captures extensive technical metadata about Objects and records actions (known as Events) taken on Objects by Agents. It also supports the addition of PREMIS Rights metadata. This page discusses how PREMIS is implemented in the AIP METS file.

On this page:

PREMIS Events metadata
PREMIS Events list
PREMIS Agent metadata
PREMIS Rights metadata

PREMIS Events metadata¶

PREMIS Events will be recorded in separate digiprovMD sections in the METS (see METS in Archivematica for more information). PREMIS Events recorded in the METS will contain metadata for most of the following semantic units and semantic components (only if applicable):

eventIdentifier - eventIdentifierType
eventIdentifier - eventIdentifierValue
eventType
eventDateTime
eventDetail
eventOutcomeInformation - eventOutcome
eventOutcomeDetail - eventOutcomeDetailNote
linkingAgentIdentifier - linkingAgentIdentifierType
linkingAgentIdentifier - linkingAgentIdentifierValue

For more information on semantic units and semantic components in PREMIS, please see the Data Dictionary. Below is an example of a PREMIS Event for file format identification.

    <mets:digiprovMD ID="digiprovMD_54">
      <mets:mdWrap MDTYPE="PREMIS:EVENT">
        <mets:xmlData>
          <premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
            <premis:eventIdentifier>
              <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
              <premis:eventIdentifierValue>b0d7f0ce-1c47-42b9-b2f1-941ca8f90bfe</premis:eventIdentifierValue>
            </premis:eventIdentifier>
            <premis:eventType>format identification</premis:eventType>
            <premis:eventDateTime>2019-11-14T11:05:37.729651+00:00</premis:eventDateTime>
            <premis:eventDetailInformation>
              <premis:eventDetail>program="Siegfried"; version="1.7.10"</premis:eventDetail>
            </premis:eventDetailInformation>
            <premis:eventOutcomeInformation>
              <premis:eventOutcome>Positive</premis:eventOutcome>
              <premis:eventOutcomeDetail>
                <premis:eventOutcomeDetailNote>fmt/353</premis:eventOutcomeDetailNote>
              </premis:eventOutcomeDetail>
            </premis:eventOutcomeInformation>
            <premis:linkingAgentIdentifier>
              <premis:linkingAgentIdentifierType>preservation system</premis:linkingAgentIdentifierType>
              <premis:linkingAgentIdentifierValue>Archivematica-1.10</premis:linkingAgentIdentifierValue>
            </premis:linkingAgentIdentifier>
            <premis:linkingAgentIdentifier>
              <premis:linkingAgentIdentifierType>repository code</premis:linkingAgentIdentifierType>
              <premis:linkingAgentIdentifierValue>12345</premis:linkingAgentIdentifierValue>
            </premis:linkingAgentIdentifier>
            <premis:linkingAgentIdentifier>
              <premis:linkingAgentIdentifierType>Archivematica user pk</premis:linkingAgentIdentifierType>
              <premis:linkingAgentIdentifierValue>1</premis:linkingAgentIdentifierValue>
            </premis:linkingAgentIdentifier>

Note that there will be three Agents per Event listed under the linkingAgentIdentifier semantic unit. This means there will also be three linkingAgentIdentifierType and three linkingAgentIdentifierValue semantic components. Each Agent applied to a PREMIS event will also have its own digiprovMD section in the METS (see PREMIS Agent Metadata).

PREMIS Events list¶

There are PREMIS Events that apply to original files and some that apply to normalized files. Both are listed below, followed by a list of Events that occur when certain microservices run in Archivematica.

Skip to:

Default events for original files
Normalized files
Filename change
Format identification
Extract packages
OCR transcription
AIP reingest
Sending transfers to backlog

Default events for original files¶

The following microservices are run for all original objects ingested into Archivematica, including any submission documentation:

ingestion
message digest calculation
virus check

If a bag or a transfer with checksum manifests is ingested, then each file will include:

fixity check

Normalized files¶

The following microservices are run for all normalized files:

creation
message digest calculation
validation (if there is a validation tool available for the identified format)

Note that for original files with a normalized derivative, a normalization PREMIS Event will be added.

<mets:digiprovMD ID="digiprovMD_17">
  <mets:mdWrap MDTYPE="PREMIS:EVENT">
    <mets:xmlData>
      <premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
        <premis:eventIdentifier>
          <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
          <premis:eventIdentifierValue>d7746761-d98c-4a78-80e0-2e91e4c187d4</premis:eventIdentifierValue>
        </premis:eventIdentifier>
        <premis:eventType>normalization</premis:eventType>
        <premis:eventDateTime>2019-11-14T11:11:29.620854+00:00</premis:eventDateTime>
        <premis:eventDetailInformation>
          <premis:eventDetail>ArchivematicaFPRCommandID="a34ddc9b-c922-4bb6-8037-bbe713332175"; program="convert"; version="Version: ImageMagick 6.9.7-4 Q16 x86_64 20170114 http://www.imagemagick.org"
</premis:eventDetail>
        </premis:eventDetailInformation>
        <premis:eventOutcomeInformation>
          <premis:eventOutcome></premis:eventOutcome>
          <premis:eventOutcomeDetail>
            <premis:eventOutcomeDetailNote>%SIPDirectory%objects/View_from_lookout_over_Queenstown_towards_the_Remarkables_in_spring-d8717b3a-d12c-408a-9c37-732425331f44.tif</premis:eventOutcomeDetailNote>
          </premis:eventOutcomeDetail>
        </premis:eventOutcomeInformation>

Filename change¶

If this microservice is run on a file, then it is entered as the following PREMIS Event which also records the original filename:

filename change

<mets:digiprovMD ID="digiprovMD_11">
  <mets:mdWrap MDTYPE="PREMIS:EVENT">
    <mets:xmlData>
      <premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
        <premis:eventIdentifier>
          <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
          <premis:eventIdentifierValue>842774e2-7eeb-49a2-99ee-eade80f6bd1f</premis:eventIdentifierValue>
        </premis:eventIdentifier>
        <premis:eventType>filename change</premis:eventType>
        <premis:eventDateTime>2020-01-06T15:01:52.881142+00:00</premis:eventDateTime>
        <premis:eventDetailInformation>
          <premis:eventDetail>prohibited characters removed: program="sanitize_names"; version="1.10.db4f6aca278e6daf2af160ed40349baf7c6f53af"</premis:eventDetail>
        </premis:eventDetailInformation>
        <premis:eventOutcomeInformation>
          <premis:eventOutcome></premis:eventOutcome>
          <premis:eventOutcomeDetail>
            <premis:eventOutcomeDetailNote>Original name="%transferDirectory%objects/(brackets)/@at.txt"; new name="%transferDirectory%objects/(brackets)/_at.txt"</premis:eventOutcomeDetailNote>
          </premis:eventOutcomeDetail>
        </premis:eventOutcomeInformation>

Format identification¶

When this microservice is run, the following PREMIS Events may be recorded:

format identification
validation (if there is a validation tool available for the identified format)

Extract packages¶

This PREMIS Event will be recorded on all extracted files:

unpacking

<mets:digiprovMD ID="digiprovMD_54">
  <mets:mdWrap MDTYPE="PREMIS:EVENT">
    <mets:xmlData>
      <premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
        <premis:eventIdentifier>
          <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
          <premis:eventIdentifierValue>bfeecc68-855c-41ad-a628-37c2a1fb2142</premis:eventIdentifierValue>
        </premis:eventIdentifier>
        <premis:eventType>unpacking</premis:eventType>
        <premis:eventDateTime>2020-03-05T18:02:26.966342+00:00</premis:eventDateTime>
        <premis:eventDetailInformation>
          <premis:eventDetail>Unpacked from: %transferDirectory%objects/Project.zip (63706dd1-6f8f-4460-a5a5-546bac061d91)</premis:eventDetail>
        </premis:eventDetailInformation>
        <premis:eventOutcomeInformation>

OCR transcription¶

If OCR is run over a file in the Ingest tab, then the file will include the following PREMIS Event:

transcription

AIP reingest¶

If an AIP has been partially or fully reingested there will be a PREMIS Event for all files in the objects directory:

reingestion

Sending transfers to backlog¶

If a transfer was sent to backlog there will be an PREMIS Event:

removal from backlog

<mets:digiprovMD ID="digiprovMD_11">
  <mets:mdWrap MDTYPE="PREMIS:EVENT">
    <mets:xmlData>
      <premis:event xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
        <premis:eventIdentifier>
          <premis:eventIdentifierType>UUID</premis:eventIdentifierType>
          <premis:eventIdentifierValue>de7463a9-1ecd-4499-b692-b61034290452</premis:eventIdentifierValue>
        </premis:eventIdentifier>
        <premis:eventType>removal from backlog</premis:eventType>
        <premis:eventDateTime>2019-11-18T12:24:38.892676+00:00</premis:eventDateTime>
        <premis:eventDetailInformation>

PREMIS Agent metadata¶

PREMIS Agents that are linked to a PREMIS Event will also be placed in its own digiprovMD section. The default semantic units for each agent are:

agentIdentifier
agentName
agentType

There are three types of Agents associated with every PREMIS Event. They will be listed under agentType as the following three options (METS XML examples included):

Software¶

    <mets:digiprovMD ID="digiprovMD_57">
      <mets:mdWrap MDTYPE="PREMIS:AGENT">
        <mets:xmlData>
          <premis:agent xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
            <premis:agentIdentifier>
              <premis:agentIdentifierType>preservation system</premis:agentIdentifierType>
              <premis:agentIdentifierValue>Archivematica-1.10</premis:agentIdentifierValue>
            </premis:agentIdentifier>
            <premis:agentName>Archivematica</premis:agentName>
            <premis:agentType>software</premis:agentType>
          </premis:agent>

Organization¶

    <mets:digiprovMD ID="digiprovMD_58">
      <mets:mdWrap MDTYPE="PREMIS:AGENT">
        <mets:xmlData>
          <premis:agent xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
            <premis:agentIdentifier>
              <premis:agentIdentifierType>repository code</premis:agentIdentifierType>
              <premis:agentIdentifierValue>12345</premis:agentIdentifierValue>
            </premis:agentIdentifier>
            <premis:agentName>XYZ Library</premis:agentName>
            <premis:agentType>organization</premis:agentType>
          </premis:agent>

Archivematica user¶

    <mets:digiprovMD ID="digiprovMD_59">
      <mets:mdWrap MDTYPE="PREMIS:AGENT">
        <mets:xmlData>
          <premis:agent xmlns:premis="http://www.loc.gov/premis/v3" xsi:schemaLocation="http://www.loc.gov/premis/v3 http://www.loc.gov/standards/premis/v3/premis.xsd" version="3.0">
            <premis:agentIdentifier>
              <premis:agentIdentifierType>Archivematica user pk</premis:agentIdentifierType>
              <premis:agentIdentifierValue>1</premis:agentIdentifierValue>
            </premis:agentIdentifier>
            <premis:agentName>username="analyst", first_name="Jane", last_name="Smith"</premis:agentName>
            <premis:agentType>Archivematica user</premis:agentType>
          </premis:agent>

One of each type of Agent will be included in each amdSec as its own digiprovMD in the METS AIP file (See METS in Archivematica).

PREMIS Rights metadata¶

PREMIS rights metadata can be added during transfer or ingest; it can be entered via the GUI interface to be applied to the entirety of the SIP or transfer. Rights can also be entered at the object level by describing them in a rights.csv file and using the Import metadata feature.

Below, the entry template is described as it appears for each rights basis, followed by acts granted/restricted.

Skip to:

Basis: Copyight
Basis: Statute
Basis: License
Basis: Donor
Basis: Policy
Basis: Other
Acts granted or restricted

Basis: Copyright¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

PREMIS in METS XML: <premis:rightsBasis>Copyright</premis:rightsBasis>

Copyright status¶

Rule “A coded designation of the copyright status of the object at the time the rights status is recorded; e.g. copyrighted, publicdomain, unknown.”

<premis:rightsStatement>
    <premis:copyrightInformation>
       <premis:copyrightStatus>Under copyright</premis:copyrightStatus>

Copyright jurisdiction¶

Rule “The country whose copyright laws apply”

<premis:rightsStatement>
   <premis:copyrightInformation>
       <premis:copyrightJurisdiction>ca</premis:copyrightJurisdiction>

Notes Values should be taken from a controlled vocabulary. Recommended: ISO 3166.

Copyright determination date¶

Rule “The date that the copyright status recorded in copyrightStatus was determined.”

<premis:rightsStatement>
    <premis:copyrightInformation>
         <premis:copyrightStatusDeterminationDate>2011-09-16</premis:copyrightStatusDeterminationDate>

Notes Uses ISO 8061.

Copyright start date¶

Rule “Date when the particular copyright applies or is applied to the content.”

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightApplicableDates>
         <premis:startDate>2015-01-01</premis:startDate>

Notes Uses ISO 8061.

Copyright end date¶

Rule “Date when the particular copyright no longer applies or is applied to the content.”

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightApplicableDates>
         <premis:endDate>2065-01-01</premis:endDate>

Notes Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Copyright documentation identifier- Type¶

Rule “A designation of the domain within which the copyright documentation identifier is unique.”

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightDocumentationIdentifier>
         <premis:copyrightDocumentationIdentifierType> Donor form </premis:copyrightDocumentationIdentifierType>

Copyright documentation identifier- Value¶

Rule “The value of the copyrightDocumentationIdentifier.”

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightDocumentationIdentifier>
         <premis:copyrightDocumentationIdentifierValue>CCA-2009-67</premis:copyrightDocumentationIdentifierValue>

Copyright documentation identifier- Role¶

Rule “A value indicating the purpose or expected use of the documentation being identified.”

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightDocumentationIdentifier>
         <premis:copyrightDocumentationIdentifierRole>Copyright holder statement</premis:copyrightDocumentationIdentifierRole>

Copyright note¶

Rule “Additional information about the copyright status of the object”.

<premis:rightsStatement>
   <premis:copyrightInformation>
      <premis:copyrightNote>Copyright held by donor</premis:copyrightNote>

Basis: Statute¶

PREMIS in METS XML: <premis:rightsBasis>Statute</premis:rightsBasis>

Statute jurisdiction¶

Rule “The country or other political body enacting the statute.”

<premis:rightsStatement>
   <premis:statuteInformation>
      <premis:statuteJurisdiction>ca</premis:statuteJurisdiction>

Notes Values should be taken from a controlled vocabulary. Recommended: ISO ISO 3166.

Statute citation¶

Rule “An identifying designation for the statute.”

<premis:rightsStatement>
   <premis:statuteInformation>
      <premis:statuteCitation>Freedom of Information and Protection of Privacy Act [RBSC 1996] Chapter 165</premis:statuteCitation>

Statute determination date¶

Rule “The date that the determination was made the the statute authorized the permission(s) noted.”

<premis:rightsStatement>
   <premis:statuteInformation>
      <premis:statuteInformationDeterminationDate>2015-07-02</premis:statuteInformationDeterminationDate>

Note Uses ISO 8061

Statute start date¶

Rule “The date when the statute begins to apply or is applied to the content.”

<premis:rightsStatement>
   <premis:statuteApplicableDates>
      <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061

Statute end date¶

Rule “The date when the statute ceases to apply or is applied to the content.”

<premis:rightsStatement>
   <premis:statuteApplicableDates>
      <premis:endDate>2020-01-01</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Statute documentation identifier- Type¶

Rule “A designation of the domain within which the statute documentation identifier is unique.”

<premis:rightsStatement>
   <premis:statuteDocumentationIdentifier>
      <premis:statuteDocumentationIdentifierType>Acts</premis:statuteDocumentationIdentifierType>

Statute documentation identifier- Value¶

Rule “The value of the statuteDocumentationIdentifier.”

<premis:rightsStatement>
   <premis:statuteDocumentationIdentifier>
      <premis:statuteDocumentationIdentifierValue>RBSC 1996</premis:statuteDocumentationIdentifierValue>

Statute documentation identifier- Role¶

Rule “A value indicating the purpose or expected use of the documentation being identified.”

<premis:rightsStatement>
   <premis:statuteDocumentationIdentifier>
      <premis:statuteDocumentationIdentifierRole>Law</premis:statuteDocumentationIdentifierRole>

Statute note¶

Rule “Additional information about the statute.”

<premis:rightsStatement>
   <premis:statuteInformation>
      <premis:statuteNote>Social insurance numbers, health information covered by personal privacy provisions</premis:statuteNote>

Basis: License¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

PREMIS in METS XML: <premis:rightsBasis>License</premis:rightsBasis>

License terms¶

Rule “Text describing the license or agreement by which permission was granted.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseTerms>This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license</premis:licenseTerms>

License start date¶

Rule “The date at which the license is first applies or is applied to the content.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseApplicableDates>
         <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061.

License end date¶

Rule “The date at which the license no longer applies or is applied to the content.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseApplicableDates>
         <premis:endDate>OPEN</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date” as: shown above.

License documentation identifier- Type¶

Rule “A designation of the domain within which the license documentation identifier is unique.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseDocumentationIdentifier>
         <premis:licenseDocumentationIdentifierType>Accession form number</premis:licenceDocumentationIdentifierType>

License documentation identifier- Value¶

Rule “The value of the licenseDocumentationIdentifier.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseDocumentationIdentifier>
         <premis:licenseDocumentationIdentifierValue>CCA-2011-29</premis:licenseDocumentationIdentifierValue>

License documentation identifier- Role¶

Rule “A value indicating the purpose or expected use of the documentation being identified.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseDocumentationIdentifier>
         <premis:licenseDocumentationRole>Accession form license area</premis:licenseDocumentationRole>

License note¶

Rule “Additional information about the license.”

<premis:rightsStatement>
   <premis:licenseInformation>
      <premis:licenseNote>Donors are prompted to choose a Creative Commons license on accession form</premis:licenseNote>

Basis: Donor¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

Note

Archivematica provides a template for donor rights, which are translated in PREMIS as “other”. In the METS file, you will find Donor rights in a rightsMD <premis:rightsBasis>Other</premisrightsBasis>.

Donor agreement start date¶

Rule “Date when the other right applies or is applied to the content.”

<premis:rightsStatment>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061.

Donor agreement end date¶

Rule “Date when the other right no longer applies or is applied to the content.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:endDate>2025-01-01</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Donor documentation identifier- Type¶

Rule “A designation of the domain within which the rights statement documentation identifier is unique.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierType>Donor form number</premis:otherRightsDocumentationIdentifierType>

Donor documentation identifier- Value¶

Rule “The value of the otherRightsDocumentationIdentifier.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierValue>CCA-2011-89</premis:otherRightsDocumentationIdentifierValue>

Donor documentation identifier- Role¶

Rule “The value indicating the purpose or expected use of the documentation being identified.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierRole>Agreement</premis:otherRightsDocumentationIdentifierRole>

Donor agreement note¶

Rule “Additional information about the rights of the object”.

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsNote>Ten-year restriction on access by donor request</premis:otherRightsNote>

Basis: Policy¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

Note

Archivematica provides a template for policy rights, which are translated in PREMIS as “other”. In the METS file, you will find Policy rights in a rightsMD <premis:rightsBasis>Other</premisrightsBasis>.

Policy start date¶

Rule “Date when the other right applies or is applied to the content.”

<premis:rightsStatment>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061.

Policy end date¶

Rule “Date when the other right no longer applies or is applied to the content.”

METS XML

<premis:rightsStatement>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:endDate>2025-01-01</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Policy documentation identifier- Type¶

Rule “A designation of the domain within which the rights statement documentation identifier is unique.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierType>RFA policy number</premis:otherRightsDocumentationIdentifierType>

Policy documentation identifier- Value¶

Rule The value of the otherRightsDocumentationIdentifier

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierValue>RFA-P-1992/040</premis:otherRightsDocumentationIdentifierValue>

Policy documentation identifier- Role¶

Rule “The value indicating the purpose or expected use of the documentation being identified.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsDocumentationIdentifier>
         <premis:otherRightsDocumentationIdentifierRole>Policy</premis:otherRightsDocumentationIdentifierRole>

Policy note¶

Rule “Additional information about the rights of the object”.

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsNote>Thirty-year closure rule: Executive Office records available only to Richards Foundation staff and BoD</premis:otherRightsNote>

Basis: Other¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

PREMIS in METS XML: <premis:rightsBasis>Other</premisrightsBasis>

Other rights basis¶

Rule “Designation of the basis for the other right or permission described in the rightsStatementIdentifier.”

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsBasis>Agreements</premis:otherRightsBasis>

Other start date¶

<premis:rightsStatment>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061.

Other end date¶

<premis:rightsStatement>
   <premis:otherRightsInformation>
     <premis:otherRightsApplicableDates>
        <premis:endDate>2025-01-01</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Note¶

Rule “Additional information about the rights of the object”.

<premis:rightsStatement>
   <premis:otherRightsInformation>
      <premis:otherRightsNote>Terms of MOU with depositor include 10-year embargo for access</premis:otherRightsNote>

Acts granted or restricted¶

Below is a list of the template fields and the associated rule. The example also includes the resulting block of METS XML.

Act¶

Rule “The action the preservation repository is allowed to take; e.g. replicate, migrate, modify, use, disseminate, delete.”

<premis:rightsStatement>
   <premis:rightsGranted>
      <premis:act>Delete</premis:act>

Grant/restriction¶

Rule Drop-down field: choose between Allow, Disallow, Conditional

<premis:rightsStatement>
   <premis:rightsGranted>
      <premis:restriction>Disallow</premis:restriction>

Start¶

Rule “Beginning date of the rights or restrictions granted.”

<premis:rightsStatement>
   <premis:rightsGranted>
      <premis:termOfRestriction>
         <premis:startDate>2015-01-01</premis:startDate>

Note Uses ISO 8061.

End¶

Rule “Ending date of the rights or restrictions granted.”

<premis:rightsStatement>
   <premis:rightsGranted:
      <premis:termofRestriction>
         <premis:endDate>2025-01-01</premis:endDate>

Note Uses ISO 8061. End date can be left open by clicking “Open End Date.”

Grant/restriction note¶

Rule “Additional information about the rights granted.”

<premis:rightsStatement>
   <premis:rightsGranted>
      <premis:rightsGrantedNote>Publication restricted until copyright expires.</premis:rightsGrantedNote>

Back to the top

PREMIS metadata in Archivematica¶

PREMIS Events metadata¶

PREMIS Events list¶

Default events for original files¶

Normalized files¶

Filename change¶

Format identification¶

Extract packages¶

OCR transcription¶

AIP reingest¶

Sending transfers to backlog¶

PREMIS Agent metadata¶

Software¶

Organization¶

Archivematica user¶

PREMIS Rights metadata¶

Basis: Copyright¶

Copyright status¶

Copyright jurisdiction¶

Copyright determination date¶

Copyright start date¶

Copyright end date¶

Copyright documentation identifier- Type¶

Copyright documentation identifier- Value¶

Copyright documentation identifier- Role¶

Copyright note¶

Basis: Statute¶

Statute jurisdiction¶

Statute citation¶

Statute determination date¶

Statute start date¶

Statute end date¶

Statute documentation identifier- Type¶

Statute documentation identifier- Value¶

Statute documentation identifier- Role¶

Statute note¶

Basis: License¶

License terms¶

License start date¶

License end date¶

License documentation identifier- Type¶

License documentation identifier- Value¶

License documentation identifier- Role¶

License note¶

Basis: Donor¶

Donor agreement start date¶

Donor agreement end date¶

Donor documentation identifier- Type¶

Donor documentation identifier- Value¶

Donor documentation identifier- Role¶

Donor agreement note¶

Basis: Policy¶

Policy start date¶

Policy end date¶

Policy documentation identifier- Type¶

Policy documentation identifier- Value¶

Policy documentation identifier- Role¶

Policy note¶

Basis: Other¶

Other rights basis¶

Other start date¶

Other end date¶

Other documentation identifier- Type¶

Other documentation identifier- Value¶

Other documentation identifier- Role¶

Note¶

Acts granted or restricted¶

Act¶

Grant/restriction¶

Start¶

End¶

Grant/restriction note¶

Archivematica 1.14.1

Contents

Search

Available projects

Archivematica

Archivematica Storage Service

License