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/1.0/basic

Directory structure:

root_directory
│── manifest-md5.txt
│── bagit.txt
│
└── data
    │── mets.xml
    │── metadata
    |   |── descriptive
    |   |   └── dc.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.

Package METS

• The csip:CONTENTINFORMATIONTYPE attribute MUST be set to https://data.hetarchief.be/id/sip/1.0/basic.
• The mets/dmdSec/mdRef/@MDTYPE attribute MUST be set to DC.

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*.xml that describes the IE.
• The dc*.xml filename SHOULD apply the following naming convention: dc*.xml with * is any string of zero or more characters.
• The dc*.xml file MUST only use the DCTERMS schema and MUST NOT use any other metadata schemas.
• The dc*.xml file MUST declare the DCTERMS namespaces in its root element.
• The dc*.xml file MUST use the <metadata/> tag as its root element.
• The dc*.xml file MUST be limited to the DCTERMS elements outlined in the table below.
• The dc*.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*.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*.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.
• A descriptive metadata element of datatype String MAY 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). The value of this attribute MUST be a valid IETF BCP 47 language tag(see here for a list).

Connecting the descriptive metadata to PREMIS

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

There is a link present between each dc*.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*.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:dcterms="http://purl.org/dc/terms/" xmlns:xs="http://www.w3.org/2001/XMLSchema/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/">


  <!-- general title for the resource -->
  <dcterms:title>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">XXXX</dcterms:created>

  <!-- multiple keywords about the resource -->
  <dcterms:subject>Cat</dcterms:subject>
  <dcterms:subject>Felis Catus Flamens</dcterms:subject>


</metadata>   

Use Cases

Some use cases that implement this profile are:

• Single file

• Video file with subtitles