Temporal Context

Collection dates, time ranges, temporal coverage

Stewardship (S)

Findable (F2)

Justification

Temporal metadata enables time-based filtering and contextual understanding of when data was collected, which is essential for reproducibility and relevance assessment. DataCite lists Date as Recommended with rich sub-types (Created, Collected, Submitted). schema.org includes temporalCoverage using ISO 8601 format. Dublin Core’s Date and Coverage elements both address temporal context.

Practical Guide

good-to-have

Add dates if applicable. Critical for time-series data.

Temporal metadata (collection dates, time ranges) lets users filter datasets by when data was collected — essential for assessing relevance and reproducibility. The very low citation ratio (0.03x) reflects that time-tagged datasets tend to be in specialized, low-citation domains. The signal measures metadata completeness, not citation potential.

Why this signal matters despite the numbers

The 0.03x citation ratio is one of the lowest, but temporal metadata is essential for reproducibility. Time-series datasets serve small, specialized communities. Dates help users assess whether data is still relevant — a value citations can't measure.

For Repositories

Add optional date fields for collection period (start/end)
Support ISO 8601 date format
Map to DataCite #8 Date or schema.org temporalCoverage

For Depositors

Include collection dates or time ranges if your data is time-bound
Use ISO 8601 format (YYYY-MM-DD) for machine readability
Specify whether dates represent collection, creation, or coverage period

Broadly useful for reproducibility context. Low prevalence (6.1%) means repositories can differentiate by supporting it.

Standards Sources

Convergence score: 4/4 independent sources —

Strongly justified

Standard	Field / Property	Obligation Level
DataCite 4.6	#8 Date	Recommended
schema.org	temporalCoverage	Recommended
Dublin Core	Date / Coverage (temporal)	Core Element

FAIR Principle Alignment

Primary mapping: Findable (F2)

F2: Data are described with rich metadata

RDA FAIR Data Maturity Model Indicators:

RDA-F2-01M: Rich metadata is provided to allow discovery

How This Signal Is Measured

Presence of ISO 8601 formatted dates, date ranges, or temporal coverage descriptions. Binary: present or absent.

Empirical Evidence (Zenodo, n=1.3M)

Per-signal statistics use Zenodo as the primary validation source because it is the largest general-purpose repository with structured DataCite metadata, natural variance across all 25 signals, and available citation/usage data. Domain-specific repositories exhibit ceiling effects or restricted variance that preclude per-signal discrimination. Cross-repository validation is reported separately.

Prevalence

6.1%

of Zenodo datasets

Citation Lift

~0x

vs. datasets without

Data Source

Zenodo (CERN)

1,328,100 records analyzed

Interpretation: Temporal metadata correlates with time-series datasets in niche domains. These serve smaller research communities. Temporal context is essential for reproducibility regardless of citation impact.