Read a data catalogue record and choose the right resource

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.

Situations and decisions

Typical situations for preparing a check. They do not describe completed assignments or actual observations.

Record to retain

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

Official references

• W3C — DCAT 3 catalogue vocabulary
• W3C — data on the Web best practices
• W3C — PROV-O provenance ontology

Related source profiles

• data.gouv.fr
• data.europa.eu
• Open Government · Canada
• DataCite Commons
• Zenodo

Related protocols

• Build a usable data dictionary
• Check the licence before reusing data
• Keep a reproducible version of public data
• Calculate and compare a file’s SHA-256 digest

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.