Editor’s Draft

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/2.1/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

• There MUST be exactly one IE.
• The IE MUST be represented by exactly one representation.
• The representation MUST contain at least one file.
• Preservation metadata MUST be limited to the PREMIS metadata schema.
• There MUST be preservation metadata at the package level in the preservation/premis.xml file.
• There MUST be preservation metadata at the representation level in the preservation/premis.xml file.
• Only the MD5 hashing algorithm is allowed to compute the fixity, thus:
  • The value of element premis:premis/premis:object[@xsi:type="premis:file"]/premis:objectCharacteristics/premis:fixity/premis:messageDigestAlgorithm MUST be set to MD5.
  • The value of attribute premis:premis/premis:object[@xsi:type="premis:file"]/premis:objectCharacteristics/premis:fixity/premis:messageDigestAlgorithm/@valueURI MUST be set to "http://id.loc.gov/vocabulary/preservation/cryptographicHashFunctions/md5".

Package METS

• The csip:CONTENTINFORMATIONTYPE attribute MUST be set to OTHER and the csip:OTHERCONTENTINFORMATIONTYPE attribute MUST be set to https://data.hetarchief.be/id/sip/2.1/basic.
• The mets/dmdSec/mdRef/@MDTYPE attribute MUST be set to OTHER and mets/dmdSec/mdRef/@OTHERMDTYPE attribute must be set to DC+SCHEMA.

Descriptive metadata

• There MUST NOT be any descriptive metadata at the representation level.
• The /descriptive directory at the package level MUST contain exactly one metadata file dc+schema.xml that describes the IE.
• The dc+schema.xml file MUST use the <metadata/> tag as its root element.
• The dc+schema.xml file MUST declare the http://purl.org/dc/terms/ (dcterms), https://schema.org/ (schema), http://www.w3.org/2001/XMLSchema-instance (xsi) and http://id.loc.gov/datatypes/edtf/ (edtf) namespaces in its root element.
• The dc+schema.xml file MUST declare https://data.hetarchief.be/id/sip/2.1/basic as default namespace in its root element.
• Descriptive metadata in dc+schema.xml MUST be limited to the DCTERMS and SCHEMA elements outlined in the table below.
• The dc+schema.xml file MUST adhere to the restrictions on cardinality of terms outlined in the table below; if a term is not listed with a restriction on cardinality, it MAY be used multiple times.
• The dc+schema.xml file MUST contain a shared ID with a PREMIS object in the preservation/premis.xml file, stored in the <dcterms:identifier> element (see next section).
• The dc+schema.xml file MUST NOT contain additional IDs besides the shared ID in the <dcterms:identifier>; these MUST be added in the preservation/premis.xml file.
• Some descriptive metadata elements of datatype String MUST contain an attribute @xml:lang that indicates the language of the metadata element’s value (in order to, for example, specify a title or description in multiple languages); these are indicated with [@xml:lang=*] in the table below. Other elements MUST NOT contain this attribute.
• The value of the @xml:lang attribute MUST be a valid IETF BCP 47 language tag(see here for a list).

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/2.1/basic" 
      xmlns:dcterms="http://purl.org/dc/terms/" 
      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>


</metadata>   

Use Cases

Some use cases that implement this profile are:

• Single file

• Video file with subtitles