Skip to content

Verify DOIs across references.bib + clean up 3 entries (#25)#34

Merged
LukasWallrich merged 2 commits into
mainfrom
verify/references-dois
Jun 28, 2026
Merged

Verify DOIs across references.bib + clean up 3 entries (#25)#34
LukasWallrich merged 2 commits into
mainfrom
verify/references-dois

Conversation

@LukasWallrich

Copy link
Copy Markdown
Contributor

First half of the final referencing pass (#25): a full DOI verification of references.bib, plus the concrete fixes it surfaced. Touches only references.bib, so no overlap with the in-flight prose PRs (#32, #33).

Verification result

Checked all 164 DOIs (190 entries total) against Crossref; OSF/Zenodo/PsychArchives DOIs (which register with DataCite, not Crossref) were re-checked against doi.org.

  • Every DOI resolves. The 11 initial Crossref "404s" were all OSF/Zenodo/PsychArchives DOIs that resolve fine via doi.org (200).
  • No wrong-paper DOIs. The low title-similarity flags (SimmonsEtAl2011, Simonsohn2015, KooleLakens2012, LakensEtz2017) are just Crossref storing the short title without the subtitle — the DOIs are correct and the bib titles are the fuller, accurate ones.
  • 26 entries legitimately have no DOI (software, websites, datasets, some books).

Fixes applied (in this PR)

  • Nagy_2025 — reformatted from a malformed single inline line (with a leading space) into the file's standard multi-line BibTeX style. Renders correctly (verified).
  • IsagerEtAl2021 — removed a stray leading space before the entry header.
  • NagyEtAl2024 — removed: an uncited PsyArXiv-preprint duplicate of the published, cited Nagy_2025 (same Bestiary of QRPs paper). No rendered output changes (it was never cited).

Flagged for your review (not changed)

Crossref reports a 2026 issue/online date for three cited works, vs the bib's year — likely online-first-vs-issue or a recent metadata re-stamp, but worth confirming the intended citation year:

  • ClarkeEtAl2024 (bib 2024 — Crossref online 2026-02) · 10.1037/amp0001385
  • PawelEtAl2023 (bib 2023 — Crossref online 2026-02) · 10.1037/met0000604
  • KapitanyKavanagh2023 (bib 2023 — Crossref issued 2026-06-19) · 10.31219/osf.io/sn5gh

Several other entries show online-first (e.g. 2020) vs issue year (2021) differences — these are normal and the bib's issue-year is a fine choice, so they were left as-is.

I did not auto-change any years, per the rule against guessing citation metadata.

The remaining half of #25 (reference completeness — chasing DOIs for the 26 DOI-less entries, and the in-text citation/formatting sweep) is best done after #33 lands, since it touches the prose chapters.

Checked all 164 DOIs in references.bib against Crossref (and OSF/Zenodo/
PsychArchives DOIs against doi.org): every DOI resolves and none point to
the wrong paper. Concrete fixes from the pass:

- Reformat the malformed inline 'Nagy_2025' entry (single line with a
  leading space) into the file's standard multi-line BibTeX style.
- Remove the leading space before the 'IsagerEtAl2021' entry header.
- Remove 'NagyEtAl2024', an uncited PsyArXiv-preprint duplicate of the
  published, cited 'Nagy_2025' (same 'Bestiary of QRPs' paper).

No DOIs were changed; ambiguous publication-year cases are flagged in the
PR for author review rather than altered.
Verified against authoritative sources that all three works flagged in
the DOI pass are actually 2026 publications, and updated their year +
key:
- ClarkeEtAl2024 -> ClarkeEtAl2026 (American Psychologist 81(2), 2026;
  the 2024 'advance online publication' note is dropped now it is in an
  issue)
- PawelEtAl2023 -> PawelEtAl2026 (Psychological Methods 31(1), 2026)
- KapitanyKavanagh2023 -> KapitanyKavanagh2026 (OSF preprint posted
  2026-06-19 per the OSF API)

Also fix a pre-existing rendering bug on the Kapitány & Kavanagh citation:
a bare '@key.' at the start of a list-continuation line made Pandoc drop
the citation and spin the rest of the sentence into a phantom example
list. Moving the citation off the line start (and closing a stray '(')
restores it. Verified: all three now render '2026' in text and refs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant