teaching-phd-skills

Why this exists

A paper that says “code available on request” is a paper whose code will not be available in four years, because the student has graduated and the laptop is gone. A deposit makes it citable and permanent. The part students get wrong is not the deposit — Zenodo’s GitHub integration is close to one click — it is which of the two DOIs goes where, and getting that backwards means your paper cites a moving target or your citation file pins a snapshot nobody should be citing.

External material

Zenodo’s GitHub integration guide for the mechanics of linking a repo and triggering a deposit from a release. The Turing Way on persistent identifiers for the concepts.

Governing part

The standard rules on the version DOI versus concept DOI distinction, and on what CITATION.cff carries. This distinction is the entire skill and is deliberately not restated here — go and read it before you deposit, not after.

The mechanic

  1. Link the repo to Zenodo.
  2. Tag a release. The deposit captures the tag, so tag something you would want a stranger to run.
  3. Collect both DOIs.
  4. Put each in the place the standard specifies.
  5. Verify CITATION.cff parses — GitHub shows a “Cite this repository” button when it does, and silently shows nothing when it does not, which is how a broken file goes unnoticed for a year.

Deliverable

Zenodo record URL.

Competency check

Turning it in

This replaces your arithmetic entry for the week you do it. Submit it to that week’s WA assignment in Canvas — the same one you would have submitted anyway. It is not an extra piece of work on top of the log.

You do not submit anything to the milestone yet. When all four skills in M6 are done, submit the M6 — Stewardship assignment, which is just an index saying which week each one went in.