In-depth practical guides

Read a data catalogue record and choose the right resource

Distinguish dataset, distribution, service and catalogue record before downloading or citing public data.

Updated :

File and table checks at an organised workstation.

AI-generated illustration

Which resource actually supported your analysis?

A catalogue can describe data without hosting its files. DCAT links these objects, but portals may leave properties incomplete. Use the record to find the producer and analysed version.

  1. Separate objects

    Identify dataset, catalogue record, distributions and access services. A CSV and an API do not automatically represent the same extract.

  2. Choose a distribution

    Check format, coverage, unit, language and period. Distinguish landing page from direct download; record the selected resource.

  3. Read dates and rights

    Separate record modification, dataset publication and file revision. Check the relevant licence and restrictions; public access alone does not establish reuse rights.

  4. Preserve lineage

    Link file, producer, extract and transformations. Retain checksum and parameters; identify who performed cleaning.

Reading workshop

Choose a resource within DEMO-D12

This catalogue is entirely fictional. Four linked objects have different periods and documentary roles.

Fictional data and records for learning: none of these results comes from a live service query.

Study March without replacing history with the present

The DEMO-D12 record links a March CSV, an annual ZIP and a current API. Its description is corrected in June. The aim is to document the state published for March, rather than the latest available state.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Study March without replacing history with the present
Fictional objectContent or rolePossible useSeparate check
March 2026 CSVMonthly distributionCandidate for the March studyCheck this distribution’s version, fields and licence.
2025 annual ZIPDistribution covering another periodHistorical context only hereDo not add it to the CSV; read its own rights.
Current APIService returning the current stateCurrent monitoring, subject to parametersRetain request and response; check service coverage and rights.
Record modified in JuneCatalogue descriptionExplain a metadata changeDoes not establish a revision of the March CSV.

Which resource should be considered first for the historical question?

Open each proposition to compare its diagnosis. More checks may still be needed.

The API, because it is newer

Not without checking that it returns the required version. A current response may include later revisions.

The March CSV, after checking coverage and version

Yes, as a documented candidate. Identify the exact file and check applicable rights before reuse.

The annual ZIP added to the CSV

No: periods and aggregation differ. Being in the same dataset does not make that sum meaningful.

Fictional selection record

Dataset: DEMO-D12
Question: state published for March 2026
Selected resource: March CSV distribution
Record: description corrected in June
File version: to be checked
Distribution licence: not yet verified

“Not verified” marks an open action, not permission to reuse. Record date and file version remain separate fields.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

Two files on one record

In a fictional case, monthly CSV and yearly archive share a title. Choose the period and retain distribution identity; do not sum both versions.

Updated metadata

An illustrative record’s date changes after its description is corrected. This alone does not establish revised observations.

Guided reading of an excerpt

A recent catalogue record may describe an older resource

The fictional catalogue links a dataset, an April distribution and a current service. Updating its record does not make these resources interchangeable.

Fictional exercise: identifiers, values and dates illustrate the check. This excerpt is not a live collected response.

  1. Identify the dataset

    D-42 names the overall subject. It does not identify the version actually analysed.

  2. Choose the period

    D-42-2026-04 announces an April distribution. Verify coverage and content, not merely its name.

  3. Distinguish the service

    API-live provides current access. Historical analysis needs a suitable snapshot or documented parameters.

Fictional catalogue relationships

dataset: D-42
distribution: D-42-2026-04
mediaType: text/csv
period: 2026-04
service: API-live

What to inspect

Record date
A description correction does not prove observations were revised.
Used version
Retain distribution or query, period, consultation and transformations.
Is the newest service necessarily best for studying April?

Reasoning

No. The resource must match the required period and version. A current service may have revised data; an older distribution also needs checking before use.

Official references : W3C — DCAT 3

Worked exercise

A recent record for old observations

Fictional example: the values and documents teach the method and do not describe a real organisation.

No new observation year is announced. You need data to answer a question about 2026.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
ObjectTime referenceReference type
Catalogue record2026Record update
CSV2015–2020Observation period
Documentation2026Documentation correction

Your checks

  1. Read file coverage and each distribution's role.
  2. Separate record updates from observation updates.
  3. Choose the resource for the requested period.
Read the answer

Answer and decision

The 2026 update does not make observations current. The CSV covers six years through 2020. For a 2026 question, find an appropriate distribution or state the gap. Corrected documentation may change interpretation without adding observations.

If the case changes

If a 2026 CSV exists on the same record, compare its ID, dimensions and coverage before replacing the old one.

Record to retain

Keep distribution ID, coverage, file date, documentation and selection reason.

Documentation reference : W3C — DCAT 3, temporal coverage · Consulted on

Record to retain

  • Dataset and distribution identifiers
  • Producer and cited licence
  • Access URL and downloaded file
  • Period, version, checksum and transformations

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Is the exact file identified?
  • Does the licence cover it?
  • Does the date describe the right object?
  • Are transformations recorded?

A record connecting metadata to the exact file and its reuse conditions.

Frequently asked questions

Is an access page a direct file link?

Not necessarily. It may offer several distributions or a service. Keep the page and actual resource obtained.

Does a checksum establish quality?

No. It identifies identical bytes. Definitions, coverage and accuracy require other checks.

What date to quote for a data dataset?

Specificate its role: observed period, version, publication or download. Several dates may be needed to allow the reader to understand the state used and the timeliness of the measured phenomenon.

TOOLS / REGISTERS

Information to record

Link file, producer, extract and transformations. Retain checksum and parameters; identify who performed cleaning.

  • Access date and time zone
  • Exact URL
  • Document identifier
  • Producer / publisher
  • Version / revision
  • Reference period
  • Licence / reuse rights
  • Logical type and format
  • Method / definition
  • Limit / uncertainty
  • Decision / next action
  • Review owner
  • Next review

DOCUMENTED REFERENCE

Distinguish a dataset, distribution and service

When two links appear to describe the same data, compare their objects before counting two sources. Organise collection so each value can be traced to the representation actually consulted.

DatasetDistributionDataServicedcat:distributiondcat:accessService
Distinguish a dataset, distribution and service
ReferenceValue or formWhat it identifies
dcat:Datasetdcat:distributionDataset.
dcat:Distributiondcat:accessServiceAccessible representation of the dataset.
dcat:DataServicedcat:endpointURLService providing data access.

Implication for the record

Record the catalogue entry, representation, any query and applicable licence together. Two formats of one dataset are not independent confirmations. A catalogue date does not date every observation.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

Europeana EDM: distinguish object, digital resource and rights

Europeana separates the described cultural heritage object from its web representations. This prevents treating a catalogue page as an image file or one representation’s rights as universal. Class and property names follow EDM documentation checked 22 October 2026.

edm:ProvidedCHOore:AggregationWebResourceaggregatedCHOisShownBy / hasView
Europeana EDM: distinguish object, digital resource and rights
ReferenceValue or formWhat it identifies
edm:ProvidedCHOCultural heritage objectThe supplied heritage object, including born-digital objects. Its creation date is not automatically a digitised-file date.
edm:WebResourceDigital representationA web-accessible digital representation. Several resources may represent one object with their own characteristics and rights.
ore:AggregationProvider aggregationAggregation groups links and provider provenance around the object; not a new image file or work.
edm:isShownAtContextual pageContextual view of the object, often a presentation page; not guaranteed reusable image bytes.
edm:isShownByDigital objectLink to the online digital object. Check media type and actual response before assuming JPEG or embedding.
edm:hasViewAdditional viewAdditional view, such as a detail or another representation. Multiple views do not establish multiple heritage objects.
edm:rightsResource / aggregationA resource can carry specific rights; documentation explains aggregation-rights fallback when representation-specific rights are absent.
edm:dataProviderContributing institutionInstitution contributing data, possibly through an aggregator. Not necessarily the direct technical provider or object creator.

Implication for the record

Retain exact representation URL, rights, credit and modifications. Documentation describes differing rights for different-resolution versions; thumbnail rights do not automatically extend to high resolution. Open the provider record when context is incomplete.

Can edm:isShownAt be used directly in an image element?

Only after checking: it may be an HTML context page. Identify the representation, check media type and rights, then credit object and provider.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

OAI-PMH: resume harvesting without losing dates or deletions

OAI-PMH 2.0 distinguishes items, metadata formats and disseminated records. Document version 8 January 2015 defines date selection and partial-list resumption. Diagram counts are protocol examples, not measured HAL or OpenAIRE totals.

100resumptionToken ≠ ""75resumptionToken = ""175 = 100 + 75
OAI-PMH: resume harvesting without losing dates or deletions
ReferenceValue or formWhat it identifies
datestampMetadata creation / change / deletionMetadata record creation, modification or deletion date, not automatically publication date.
from · untilInclusive boundsBoth bounds are inclusive. Resuming at the same bound can overlap prior records; check identifiers.
granularityDay / optional secondDay granularity is mandatory, optional seconds support declared by Identify. Do not invent precision.
resumptionTokenExclusive argument, with verbResume with token and verb, without adding initial selection arguments. Tokens are opaque and may expire or become invalid.
completeListSizeOptional estimateOptional complete-list size can be an estimate and change during traversal. Missing is not zero; count actual records.
header status="deleted"No metadata or aboutDeleted records retain a header without metadata or about. Do not replace this state with empty-field records.
deletedRecordno · transient · persistentIdentify declares deletion tracking: no, transient without persistence guarantee, or persistent history.
Protocol example175 = 100 + 75Official example splits 175 records into 100 and 75. Final token is empty; short-page logic is not a universal OAI stopping rule.

Implication for the record

Keep identifier, metadataPrefix and datestamp. One deleted format does not establish deletion of every format for the item. Document boundary overlap and deduplication; absent deletion history cannot be reconstructed automatically.

Can from accompany the next resumptionToken request?

No for these resumption requests: token is exclusive apart from verb. Changed selection requires a new query, tracked as a distinct traversal.

Primary documentation

Documentation consulted on .

DOCUMENTED REFERENCE

A corrected version and a new period are different relationships

An annual release and a correction to the same file serve different purposes. DCAT 3 describes resource versions and datasets belonging to a series explicitly; these links do not replace reading the methodology.

A corrected version and a new period are different relationships
ReferenceValue or formWhat it identifies
dcat:hasVersionresource → versionLinks a resource to one of its versions. Record the identifier of the version actually consulted, not only the catalogue URL.
dcat:previousVersionnew → previousLinks a version to its predecessor. Revisions can change older observations: compare release notes before calculating a trend.
dcat:inSeriesdataset → seriesPlaces a dataset in a series. Successive annual datasets can belong to a series without being corrective versions of the same dataset.

Implication for the record

Reading example: releases covering 2024 and 2025 form a temporal sequence; a corrected 2024 file still covers 2024. Check the observation period, publication date, revision and distribution format separately.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Move from metadata to the available file

A catalog describes a dataset, but the downloaded resources may have different formats or versions. The reading must bring the descriptive file and accessible files closer.

Updated on .

Priority checks

Release producer, dates, resources, formats, licenses and documentation. Open the files to check fields, coverage and correspondence with the description.

Interpretation pitfalls

A date of update of the catalog does not guarantee a new measure. A resource may be unavailable or only cover a part of the dataset described.

Working record to retain

The catalog sheet retains metadata, chosen resource, date of download and deviations. It serves as a starting point for data assessment.