Public sources / INT

Zenodo

Find deposited datasets, software, publications and other research objects with metadata and identifiers.

Consultation of scientific publications and bibliographic references.

AI-generated illustration

Read this source in practice

Should the concept or a specific version be cited?

Zenodo distinguishes a version DOI and a concept DOI representing all versions.

Checks to perform

  1. For reproducibility, record the version actually used and its DOI; mention later versions separately.
  2. Keep the analysed version DOI, filenames and analysis-code version; attach these to the result rather than recording only the concept DOI.
  3. Do not construct an address by appending “.v2” to a DOI: follow the published version relationship and check the files actually retrieved.

The reference documents the reading method. The example is fictional; this note does not attest a portal test today or a mission outcome.

On a small screen, scroll the table horizontally to read all columns.

Choose the reference fixing the analysed material
Fictional objectRowsReference to keep
Version 1100Version 1 DOI
Version 2105Version 2 DOI
ConceptV1 + V2Evolving collection: specify the version used

Interpretation limit

A general reference to an evolving object does not fix the analysed files.

Record to retain

Record identifier, scope, access date and passage supporting the conclusion.

Consulted reference : Zenodo · DOI versioning · Consulted on

Updated on :

Provenance and evidence type

Operator or reference institution
CERN
Result type
Research deposit

Compare files, version, licence and depositor. A deposit does not establish peer review or reproducibility.

What this source helps you find

Find deposited datasets, software, publications and other research objects with metadata and identifiers.

Limit to retain in your conclusion

Retain the version and licence of the file used; public deposit does not guarantee reproducibility or content quality.

Useful search anchors

  • DOI / publication title
  • Exact query

Fields to record when citing a result

  • DOI / publication title
  • Version / revision
  • Licence / reuse rights
  • Publication date

Evidence record to retain

Version DOI, record number, filenames, software version and licence.

Check before drawing a conclusion

Keep the analysed file; later versions may change data or code.

Official reference page

Access, download and API conditions depend on the service. Consult the official documentation and the resource terms.

Before export or reuse

Coverage
INT
Identifiers to retain
DOI / publication title · Version / revision · Licence / reuse rights · Publication date

Licence and rights

Inspect the exact resource and its terms. Being viewable does not authorise redistribution; retain the resource licence and restrictions instead of inferring them from the portal.

Date and version

Record consultation date, covered period, last update and version separately. For revised data, retain the file or exact extraction reference.

What object does the result describe?

Result unit
Deposit, file, version and resource metadata
Time reference to retain
Document or deposit version, publication and modification dates.

Documentation and access

The web page, export and API may differ in coverage or terms. Check pagination, filters, authentication, quotas and licence for the access method used.

Open producer documentation

Does a DOI prove that work was peer reviewed?

No. A DOI identifies an object. Check document type, journal, version and editorial process; datasets, preprints and reports can also have DOIs.

How can the actual file read in a repository be cited?

Retain record identifier, version, file and access date. Check links to other repositories; several hosts of one work do not become independent works.

Read a data catalogue record and choose the right resource
Sources for scientific reference verification

DOCUMENTED REFERENCE

Zenodo: three different dates in a real record

The poster DOI Versioning Done Right by Krzysztof Nowak, Alexandros Ioannidis, Chiara Bigarella and Lars Holm Nielsen provides a verifiable case. These values were read on the public page on 22 October 2026. The timeline orders events without a proportional duration scale.

2018-05-31Published2018-06-06Created2024-08-02Modified
Zenodo: three different dates in a real record
ReferenceValue or formWhat it identifies
DOI10.5281/zenodo.1256592DOI of the v1 version shown in the record. Read resource type separately.
Published2018-05-31Displayed publication date: 31 May 2018, not the record’s technical creation date.
Created2018-06-06Displayed technical creation: 6 June 2018, six days after the stated publication date. The gap does not establish an error.
Modified2024-08-02Displayed last technical modification: 2 August 2024. Alone, this establishes neither a new poster edition nor changed files.
Resource typePosterThe resource is a poster, not a journal article or dataset, despite having a DOI.
MD5edd6ea2835643855de87e55ab0d68e3cMD5 checksum advertised for zenodo-doi-versioning.pdf, transcribed from the record without claiming a file-level recalculation.

Implication for the record

Retain DOI, version, type, dates and filename separately. Zenodo allows metadata edits without creating a new version. For integrity checking, compare the advertised reference with the file actually held; reading a record does not perform that check.

Does Modified in 2024 make this a 2024 publication?

No. It describes the displayed technical modification, while Published here indicates 2018. State consultation date separately and check citation policy for the version used.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Read a source profile as a starting point

A list indicates where to look for and what limits to keep in mind. It helps to prepare a consultation but does not replace the reading of the obtained document.

Updated on .

Priority checks

Select a precise question, open the source and raise the request, result and date. Compare the possibilities announced with the information actually available at the time of the consultation.

Interpretation pitfalls

The availability of a service and its content may vary. The directory does not turn an absent, partial or ambiguous result into a definitive response.

Working record to retain

The consultation report documentes the search path, document found, useful elements and reserves. The result is included in the file with its origin.