DANS BagIt Profile v1.0.0 - Migration Supplement¶

Introduction¶

Version¶

• See DANS BagIt Profile v1

Status¶

• INTERNAL

Scope¶

This document supplements DANS BagIt Profile v1 by modifying its rules for bags used to migrate datasets from EASY to a Data Station. Clients of the Data Station SWORD2 service can ignore this document.

Overview and conventions¶

XML namespaces¶

Extra namespaces used:

Prefix	Namespace URI	Namespace documentation
am	http://easy.dans.knaw.nl/schemas/bag/metadata/agreements/	DANS deposit agreement metadata
amd	http://easy.dans.knaw.nl/easy/dataset-administrative-metadata/	DANS administrative metadata
emd	http://easy.dans.knaw.nl/easy/easymetadata/	DANS EASY metadata schema
prov	http://easy.dans.knaw.nl/schemas/bag/metadata/prov/	DANS provenance metadata schema

Requirements¶

2 Structural requirements¶

• 2.2-MIGRATION: Additionally, the metadata directory MAY contain the files metadata/amd.xml, metadata/emd.xml, metadata/provenance.xml, metadata/depositor-info/agreements.xml, metadata/depositor-info/depositor-agreement.pdf, metadata/depositor-info/depositor-agreement.txt, metadata/depositor-info/message-from-depositor.txt, metadata/license.html, metadata/license.txt, metadata/license.pdf, metadata/original/dataset.xml, metadata/original/files.xml.

3 Metadata requirements¶

3.1 metadata/dataset.xml¶

• 3.1.9-MIGRATION: Alternatively, dcmiMetadata/dcx-dai:contributorDetails/dcx-dai:author and dcmiMetadata/dcx-dai:contributorDetails/dcx-dai:organization elements MAY specify the rights holder using the role RightsHolder.

• 3.1.11: Rule does not apply to migration.

3.4 Migration-only metadata¶

• 3.4.1-MIGRATION: The file metadata/depositor-info/agreements.xml MUST adhere to DANS deposit agreement metadata.
• 3.4.2-MIGRATION: The file metadata/amd.xml is REQUIRED and MUST adhere to DANS administrative metadata.
• 3.4.3-MIGRATION: The file metadata/emd.xml is optional. If it is present it MUST adhere to DANS EASY metadata schema.
• 3.4.4-MIGRATION: The file metadata/provenance.xml is optional. If it is present it MUST adhere to DANS provenance metadata schema.

Section 4 Data Station context requirements¶

Rules do not apply to migration.

References¶

Extra references:

• DANS administrative metadata - schema for administrative metadata
• DANS EASY metadata schema - legacy schema for dataset level metadata
• DANS provenance metadata schema - metadata schema for recording provenance of datasets migrated from DANS EASY
• DANS deposit agreement metadata - schema for metadata about the agreement between DANS and the depositor