Repository navigation
Correct 33 citation dates to the publishers' own publication dates - #1247
Merged
Merged
Conversation
Audited all 72 entries in app/src/data/citations.json against each publisher's own metadata (JSON-LD datePublished, article:published_time, <time datetime>, citation_* tags, govuk first-published-at, Crossref, arXiv, press-release datelines, PDF covers), falling back to Wayback raw captures where the live page is walled off. Only the date field changes; entry order (and so the featured order) is untouched. The per-entry evidence table is in the PR description. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Mothers' Outreach Network: the publisher's archived WordPress record for the original page dates it 2 April 2023, so the 10 April Wayback upper bound is replaced. LSE CFM DP2023-16: CFM gives only "May 2023"; use the file's upload time on LSE's server (31 May 2023) instead of the PDF's compile date. Both found by the independent review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Merge audit for head
Title, URL and attribution problems are listed in the PR body under "Flagged, not changed" and are left for a follow-up. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
I checked all 72 entries in
app/src/data/citations.jsonagainst each publisher's own metadata. 33 dates were wrong and this PR corrects them. The other 39 are confirmed, or consistent with the best evidence available (noted per row). Onlydatefields change; entry order is untouched, so the featured order is unchanged.CitationsClient.tsxsorts "All citations" by date, so the corrected entries move to their right place in that list.This includes the Telegraph fix from #1246 as the identical one-line change, so the two PRs don't conflict whichever merges first.
Method
datePublished,article:published_time,<time datetime>,citation_*/bepress_*tags, GOV.UKfirst-published-at, and press-release datelines. For PDFs I read the cover or dateline, plus the landing page that links the PDF where one exists. I also used Crossref for DOIs, the arXiv API, the Hansard API, and WordPress or Squarespace JSON where the HTML has no date.web.archive.org/web/<ts>id_/<url>). A first Wayback capture is never read as a publication date; it only bounds one.Evidence
Bold verified dates are changes. Precision is to the day unless the Verified cell says otherwise. Row numbers are 0-based positions in
citations.json.Flagged, not changed
Dead URLs
Titles, attribution and content that don't match the source
Minor title differences (prefix or subtitle dropped)
URLs that redirect or block scripted clients (alive)
Testing
bunx prettier --check app/src/data/citations.jsonpasses, using the repo's prettier 3.8.1.origin/mainconfirms four things. It is the same 72 entries in the same order. Onlydatefields differ (33 of them). Every date is a validYYYY-MM-DDon or before 2026-10-09. The featured order is unchanged.citations.jsondirectly; the build and type check compile the JSON import.axiom: n/a: website data fix (citation dates), no policy change.
🤖 Generated with Claude Code