Skip to content
Documentation
Digital Preservation Services (DPS)
SIP specifications
METS.xml requirements
Requirements for dataset

Requirements for dataset

Requirements for METS.xml beyond the general SIP requirements

This is a list of requirements for the METS.xml file for packages containing datasets and databases to be delivered to the National Library of Norway. These requirements are in addition to those defined in METS.xml requirements.

Note

E-ARK provides dedicated Content Information Type Specifications for relational databases using SIARD (CITS SIARD) and geospatial data (CITS Geospatial). The National Library of Norway has not yet fully assessed how these specifications align with its own SIP requirements. If you want to submit geodata or SIARD-structured data, please contact the digital preservation team before delivery.

IDName, METS element, descriptionRequirementCardinality
NBDATASETSIP1Content Category
mets/@TYPE

The attribute mets/@TYPE MUST be used to specify the category of the content within the package, e.g., “Datasets”, “Websites”, “Mixes”, “Other”, etc. Valid values are defined in a controlled vocabulary. The vocabulary will be updated by the DILCIS Board as additional content information specifications are introduced.

For datasets and databases, mets/@TYPE MUST be one of the following values:
Datasets : Used for data encoded in a defined structure, e.g. data dumps and data exports in formats such as CSV, JSON, XML, or Parquet.
Databases : Used for a complete set of the content contained within a database, e.g. database dumps or exports.

See the vocabulary here E-ARK-CSIP-Content Category.

This is a specification of CSIP2.		MUST1..1
NBDATASETSIP2Content Information Type Specification
mets/@csip:CONTENTINFORMATIONTYPE

Used to define the specifications for the type of content information applied when the package was created. Valid values are defined in a controlled vocabulary. The attribute is mandatory for METS documents at the representation level. The vocabulary will be updated by the DILCIS Board as additional content information specifications are introduced.

For datasets and databases, the value OTHER is used (a term different from those included in the controlled vocabulary).

See the vocabulary here E-ARK-CSIP-Content Information Type.

This is a specification of CSIP4.		MUST1..1
NBDATASETSIP3Other Content Information Type Specification
mets[@csip:CONTENTINFORMATIONTYPE='OTHER']/@csip:OTHERCONTENTINFORMATIONTYPE

When mets/@csip:CONTENTINFORMATIONTYPE has the value OTHER, the attribute mets/@csip:OTHERCONTENTINFORMATIONTYPE MUST specify the type of content information.

OTHERCONTENTINFORMATIONTYPE for datasets and databases MUST be NB-SIP-DATASETS-PROFILE-1.0.

This is a specification of CSIP5.		MUST1..1

Example 

<mets:mets xmlns:csip="https://DILCIS.eu/XML/METS/CSIPExtensionMETS"
  xmlns:mets="http://www.loc.gov/METS/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xlink="http://www.w3.org/1999/xlink" OBJID="no-nb_datasett_0209202600042"
  LABEL="no-nb_datasett_0209202600042" TYPE="Datasets" csip:CONTENTINFORMATIONTYPE="OTHER"
  csip:OTHERCONTENTINFORMATIONTYPE="NB-SIP-DATASETS-PROFILE-1.0"
  PROFILE="https://earksip.dilcis.eu/profile/E-ARK-SIP-v2-2-0.xml"
  xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.w3.org/1999/xlink http://www.loc.gov/standards/mets/xlink.xsd https://DILCIS.eu/XML/METS/CSIPExtensionMETS https://earkcsip.dilcis.eu/schema/DILCISExtensionMETS.xsd"
  />
Last updated on - Github commit history ↗
Requirements for text