Profile: Basic

The basic profile supports simple cases consisting of a single media file accompanied by limited metadata.

Permalink: https://data.hetarchief.be/id/sip/3.0/basic

Example Directory structure

root_directory
│── METS.xml
│── metadata
|   |── descriptive
|   |   └── dc+schema.xml
|   └── preservation
|       └── premis.xml
│
└── representations
    └──representation_1
        │── METS.xml
        └──data
        |  |── file_1.xyz
        │  └── ...
        │
        └──metadata
          └──preservation
              └── premis.xml

Requirements

General

Only the MD5 hashing algorithm is allowed to compute the fixity, thus:

Package METS

Descriptive metadata

Rights-related descriptive agents, including rights holders, owners, licence distributors, performers, and producers, remain in dc+schema.xml. Rights statements, reuse conditions, and access policy MUST be recorded in PREMIS at the package level or representation level, as applicable. The deprecated dcterms:rights and dcterms:license elements SHOULD NOT be used for new SIPs.

For elements that require the @xml:lang attribute, it is still necessary to supply an element with @xml:lang set to nl even if there is no Dutch content available (e.g., the original title is in English or French and no translation was ever made, or the title is the same in both languages). In that case, a title in another language can be copied as if it were Dutch.

Root element

DCMI Terms elements

Schema.org elements

Validation

The XML files that are required by this profile can be validated using the following XML schema definitions:

Connecting the descriptive metadata to PREMIS

The dc+schema.xml file at the package-level contains descriptive metadata about the IE(s) of the SIP. It relies on the DCTERMS and SCHEMA metadata schema in order to facilitate a basic description with a limited number of descriptive metadata elements.

There is a link present between each dc+schema.xml file and the PREMIS Intellectual Entity in the preservation/premis.xml file via a shared ID. This shared ID is stored in the <dcterms:identifier> element of each dc+schema.xml file and in a <premis:objectIdentifier> element of each PREMIS object in the preservation/premis.xml file.

Please note that additional IDs must be dealt with in the preservation/premis.xml file via <premis:objectIdentifier> elements in which the type of ID is specified using the <premis:objectIdentifierType> element.

Example

<?xml version='1.0' encoding='UTF-8'?>
<metadata xmlns="https://data.hetarchief.be/id/sip/3.0/basic" 
      xmlns:dcterms="http://purl.org/dc/terms/" 
      xmlns:schema="https://schema.org/"
      xmlns:haRig="https://data.hetarchief.be/ns/rights/"
      xmlns:xs="http://www.w3.org/2001/XMLSchema/" 
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:edtf="http://id.loc.gov/datatypes/edtf/">


  <!-- general title for the resource -->
  <dcterms:title xml:lang="nl">Felis Catus Flamens</dcterms:title>

  <!-- linking id between dc and premis -->
  <dcterms:identifier>uuid-b21a86aa-97a3-4f7b-a9f5-4d330af641c0</dcterms:identifier>

  <!-- date unknown -->
  <dcterms:created xsi:type="edtf:EDTF-level1">XXXX</dcterms:created>

  <!-- multiple keywords about the resource -->
  <dcterms:subject xml:lang="nl">Cat</dcterms:subject>
  <dcterms:subject xml:lang="nl">Felis Catus Flamens</dcterms:subject>

  <!-- rights-related agents remain descriptive metadata -->
  <schema:copyrightHolder>
    <schema:name xml:lang="nl">Example Rights Foundation</schema:name>
  </schema:copyrightHolder>
  <haRig:owner>
    <schema:name xml:lang="nl">Voorbeeldmuseum</schema:name>
  </haRig:owner>


</metadata>   

Use Cases

Some use cases that implement this profile are:

• Single file

• Video file with subtitles