Standards and metadata profiles
Metadata standards, schemas and application profiles used to describe, identify, publish, exchange and reuse research data.
This section provides practical reference materials for selecting and applying metadata elements at dataset, repository, catalogue and disciplinary level.
Resource information
Resource type: Standards and metadata profiles
Primary audience: Researchers, data stewards, repository managers, metadata specialists, software developers and research infrastructure providers
Coverage: Core dataset metadata, DataCite, repository and catalogue profiles, metadata mappings and domain-specific extensions
Purpose: To support consistent, interoperable and machine-readable descriptions of research data and related research objects
Last reviewed: July 2026
Metadata standards and profiles
Select the resource that corresponds to the level at which metadata will be created or exchanged: an individual dataset, DOI registration, repository or catalogue integration, or a specialised scientific domain.
A practical core profile defining the minimum metadata elements needed to identify, describe, cite, access and reuse a research dataset.
An overview of DataCite metadata properties used for DOI registration, dataset citation and linking research outputs.
Repository and catalogue metadata profiles
Metadata requirements used to expose repository records to catalogues, aggregators and research infrastructures.
Domain-specific metadata profiles
Metadata profiles extending the core dataset description with elements required by particular scientific domains, methods and computational workflows.
How standards and profiles work together
Metadata standards and profiles operate at different levels. A standard provides a common conceptual or structural basis, while an application profile selects, combines and constrains elements for a particular community or implementation.
Standard
Defines common concepts, properties or rules intended for use across organisations and systems.
Metadata schema
Provides a structured set of metadata elements and rules for recording their values.
Application profile
Selects and constrains elements from one or more schemas for a defined implementation or community.
Domain profile
Adds scientific entities, properties, vocabularies and relationships required by a specific research domain or method.
Selecting the appropriate metadata profile
Begin with the system in which the metadata will be created or used. Repository deposit, DOI registration, catalogue exchange and domain-specific documentation may require different but related profiles.
For a basic dataset description: use the Core dataset metadata profile.
For DOI registration and citation: use the DataCite Metadata Schema.
For repository harvesting or catalogue integration: apply the relevant repository or catalogue application profile.
For specialised scientific data: extend the core profile with domain-specific metadata elements and controlled vocabularies.
How to select and apply a profile
1. Identify the output
Determine whether the metadata describes a dataset, software object, workflow, model, repository record or catalogue resource.
2. Identify the destination
Check the requirements of the repository, DOI provider, catalogue, aggregator or research infrastructure.
3. Select the profile
Use the applicable core, repository, catalogue or domain-specific profile and record any local extensions.
4. Validate the record
Check mandatory fields, identifiers, controlled values, mappings and the machine-readable metadata output.
Using profiles with other resources
Metadata profiles define which elements should be recorded. Guidelines explain how to prepare the information, templates provide a structure for entering it, and checklists help verify that the resulting description is complete and ready for publication or exchange.
Profile: defines the required metadata elements and validation rules.
Guideline: explains how to create and apply the metadata.
Template: provides a practical structure for recording metadata values.
Checklist: verifies that required elements and related documentation have been prepared.
Explanatory status
The materials in this section provide explanatory and implementation guidance. They do not replace the official specifications maintained by standards organisations, repository providers, identifier agencies or research infrastructures.
Standards and schemas may be updated over time. The current official version and the requirements of the destination repository or service should therefore be checked before implementing a metadata profile.