DDB Minimal Record Export

Requirements

• Drupal 10.2+ or Drupal 11
• Optional but typical: WissKI (entity type wisski_individual); any fieldable content entity type is supported

Installation

Composer (recommended)

Once a release is available on Drupal.org:

composer require drupal/ddb_minimal_record_export

Enable the module

drush en ddb_minimal_record_export -y
drush cr

Or enable DDB Minimal Record Export under Administration → Extend.

Configuration

1. Go to Administration → Configuration → Export → DDB Minimal Record (/admin/config/export/ddb-minimal-record).
2. Choose the entity type and base bundle.
3. For each MDS field, select a field path. Use additional hops for entity-reference chains (for example Object → Media → file URL).
4. Set export-side defaults (institution, metadata rights, language, and so on). Per-entity field overrides are optional.
5. Import or export the mapping as JSON to copy configuration between environments. Multiple MDS catalog / mapping versions can be stored and switched on the settings page.

Built-in help: Administration → Configuration → Export → DDB Minimal Record Help.

On entity forms for the configured type/bundle, mapped fields can show a small MR badge (red = mandatory, yellow = recommended). Disable under settings if needed.

Permissions

• Administer DDB Minimal Record mapping — Configure mappings, versions, and global defaults
• Export DDB Minimal Record LIDO — Run single-entity and bulk LIDO exports

Usage

Export

• Single entity: Use the MRD Export local task on an entity of the configured type/bundle.
• Bulk (ZIP / lidoWrap): Go to Administration → Configuration → Export → Bulk LIDO Export.

Bulk jobs are tracked in the database and processed via the Queue API (cron / queue workers) when the set is large.

Validation

• Every export is checked against the vendored digiS MDS profile XSD (LIDO 1.1 / MDS 1.0.1). Optionally fail the export when XSD validation fails (settings toggle).
• For full Schematron rules, upload the XML to diLIVa (external).