Cite what you actually used

Citing a notebook page#

Use “Cite this page” in any notebook to obtain its edition URL, access-ready reference and BibTeX record. The edition URL identifies the fixed content snapshot. The SHA-256 fingerprint identifies the structured page content and its bibliographic context.

The fingerprint covers the edition identifier, publication date, notebook identity and the complete chapter, including references and the exact definitions of its diagrams. It does not cover the surrounding site design, external websites or files reached through links.

Citing the research resource#

For an analysis of POD, cite the exact dataset version. For an implementation of VAO, cite the specification version. A citation of an explanatory notebook helps readers follow your reasoning, but does not substitute for either of those references.

Match the citation to the work performed#

Why a version DOI matters#

A project or concept record may group successive releases. For a reproducible reference, use the identifier that fixes the version you actually used. A community link helps a reader discover related work but does not identify a unique input. Keep the human-readable citation and the machine-readable identifiers together so the reference remains interpretable outside the original application.

A checksum complements a citation#

The digest answers whether a particular sequence of bytes or canonical structured content matches a recorded identity. It does not identify an author by itself, explain why a transformation was made or guarantee that an external service will remain online. Those needs are met by the citation, provenance, release documentation and preservation arrangements working together.

For this site, the downloadable metadata contains the exact canonical string that was hashed. Compare its recomputed digest with the recorded SHA-256 and retain the edition URL. If an external dataset or recording underpins the result, verify that artifact separately: the notebook’s fingerprint covers its own content and references, not the remote bytes behind each link.